Two tools with complete input schemas and descriptions, but quality varies. get_figma_data has a clear, actionable description (89 chars) and well-typed parameters with descriptions. download_figma_images has a verbose description (156 chars) and complex nested schema with good parameter documentation. However, output schemas are not documented in the source code, LLMs cannot predict return structure. No tool annotations (readOnlyHint/destructiveHint) despite clear risk profiles. Error handling and recovery guidance are absent from descriptions.

• Document output schemas for both tools. Example: 'Returns {fileData: {name, type, children[]}, components: {name, key}[], images: {nodeId, url}[]}'. Include field types and what each field represents.
• Add tool annotations via MCP SDK: mark get_figma_data with readOnlyHint=true; mark download_figma_images with destructiveHint=true (writes to filesystem).
• Enhance error handling descriptions: 'If Figma API returns 404, the file key is invalid, verify the URL. If path creation fails, check directory permissions and OS path format.'
• Clarify localPath constraints: 'Absolute path only. Use forward slashes on Unix/Mac, backslashes on Windows. No spaces or special chars except hyphens/underscores. Example: /home/user/images or C:\Users\user\images'.
• Document conditional parameter logic: 'imageRef is required if node is a raster image; omit for vector SVG. cropTransform only applies if needsCropping=true. filenameSuffix auto-appended to fileName if provided.'

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

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