The server provides 10 tools with reasonable naming (verb-prefixed: figma_status, figma_eval, figma_find, etc.) and descriptions present for all tools. However, quality is inconsistent across dimensions. Most tool descriptions are adequate (50-150 chars, well within bounds), but parameter descriptions are sparse or absent in many cases. Input schemas are present but incomplete: many lack parameter descriptions, type constraints, and ranges. No output schemas are documented anywhere in the source. Error handling exists but is minimal, the server will return errors but does not provide actionable recovery guidance for LLMs. Tool composition is reasonable (each does one thing), but several tools lack clarity on when to use them vs. alternatives (e.g., figma_find vs figma_metadata both retrieve node information). The 'figma_eval' tool is inherently risky, accepting arbitrary JavaScript code, no security constraints or validation hints are visible. Overall, this is a functional set of definitions that would work but falls short of production-grade clarity and safety.

• Document output schemas for all 10 tools. For each tool, specify the JSON structure, field types, and optional vs. required fields. Example for figma_metadata: { nodes: [{ id: string, name: string, type: string, bounds: { x: number, y: number, width: number, height: number }, fills: [{ type: string, color: string }], ... }], errors?: [{ nodeId: string, reason: string }] }
• Add strict enum constraints to figma_export 'format' parameter: { type: 'string', enum: ['PNG', 'SVG', 'PDF', 'JPG'], description: '...' }
• Expand figma_find 'selector' parameter description to explain valid syntax: 'CSS-like selector syntax: TYPE (e.g., Rectangle), [name=X] (exact match), [name*=X] (contains), "A B" (descendant), "a, b" (OR). Returns empty if no matches.'
• Add numeric bounds and default values to figma_export 'scale' parameter: { type: 'number', minimum: 0.01, maximum: 4, default: 1, description: 'Export scale factor. Values outside range are clamped to [0.01, 4].' }
• Add error recovery hints to descriptions. For figma_find: '... Returns empty array if no matches. If selection fails, try broadening the selector pattern or use figma_metadata with explicit node IDs.'
• Add constraints and guidance to figma_place_image 'filePath' parameter: 'Absolute path to local image file (PNG, JPG, SVG supported). Path must exist and be readable. Relative paths will fail.' And clarify node type: 'nodeId must be a Frame, Rectangle, or Image node.'
• Clarify figma_tokens behavior in description: 'If collection exists, returns existing variables. If not, creates it. Specify collection name to filter or create specific collections.'