Download-Figma-Images

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations present, so description carries full burden. Only states the basic action of downloading images, with no disclosure of network calls, authentication needs, rate limits, error handling, or side effects. Insufficient for a tool interacting with an external API.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence of 20 words, front-loaded with key information. Efficiently communicates core function, though could be slightly more structured (e.g., bullet points for parameter groups).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite 5 parameters and nested objects, no output schema is provided. Description lacks details on return values (what the download produces), error conditions, and prerequisite setups (e.g., Figma API credentials). Adequate for basic understanding but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds context about the tool's overall purpose but does not elaborate on parameters beyond what the schema already provides. No additional semantic value for individual parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly specifies verb 'Download', resource 'images', formats 'SVG and PNG', and selection criterion 'based on the IDs of image or icon nodes'. Distinguishes from siblings like 'download-svg-assets' which likely handle bulk downloads.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies use for specific image/icon nodes via node IDs, but does not explicitly state when to use this tool versus alternatives like download-svg-assets or extract-svg-assets. No when-not or prerequisite conditions provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.