A tool to download Figma designs and images, extract design data including typography styles and color palettes
Single tool 'figmaDesign' has a minimal description (58 chars) and critically incomplete input schema. The schema defines only 'figmaUrl' as a string with no type constraints, enums, format validation, or length limits. No output schema is documented. The description lacks WHEN to use it, WHAT it returns, or prerequisites (Figma API key requirement). No parameter descriptions beyond the tool level. Error handling is absent from the tool definition, no guidance on retryability or recovery. The tool combines multiple concerns (fetch design + fetch image + optional download) without clear separation.
Fetch Figma design data and image from a Figma URL or file ID
Input schema lacks type constraints and validation rules. 'figmaUrl' parameter has no format (URL vs file ID), length limits, or pattern. No enum or constraint guidance for LLM.
Tool description is 58 characters, below the 100-char minimum for actionable guidance. Missing WHEN to use, WHAT it returns, and that Figma API key is required.
No output schema documented. LLM cannot predict return structure (design object, image URL, base64 encoding, etc.). Breaks downstream tool chaining.
Tool combines fetch design + fetch image + optional download into one operation. Should split into separate tools (get_figma_design, get_figma_image) for composability.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 32 | 2026-07-28+ | v2 |
No error handling guidance. Errors like 'Figma API error' or 'Could not extract file ID' do not tell LLM what to do next (retry, ask user, check format).