Two tools with complete schemas and descriptions, but quality is uneven. get_figma_data has a vague description ('When the nodeId cannot be obtained...') that doesn't clearly state what the tool does or when to use it. download_figma_images has better clarity but both tools lack output schema documentation. Parameters are well-typed with Zod and mostly described, but descriptions could be more actionable. No tool annotations (readOnlyHint/destructiveHint) despite clear risk profiles. Error handling returns structured responses but lacks recovery guidance.

• Rewrite get_figma_data description to: 'Retrieve Figma file structure, design tokens, and component metadata. Optionally fetch a specific node by ID and limit traversal depth. Use this to explore file organization before requesting specific nodes or images.'
• Add explicit output schema documentation: get_figma_data returns {metadata: {name, id, ...}, nodes: [...], globalVars: [...]} as YAML; download_figma_images returns {success: boolean, files: string[]}.
• Add tool annotations: get_figma_data with readOnlyHint=true; download_figma_images with destructiveHint=true (creates files on disk).
• Enhance error messages with recovery paths: 'File not found (404). Verify fileKey format or use search_files() to list available files.' Include the invalid value in the error.
• Add parameter constraints: depth should have min=1, max=10 (or document the actual limit); fileKey should document expected format (alphanumeric, 20-30 chars typical).

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry