Get Figma Images

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

Annotations already declare readOnlyHint and openWorldHint. The description adds the token requirement and format options, but lacks details about rate limits, error handling, or URL expiration. Adequate but not beyond annotations.

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?

Extremely concise two-sentence description with no wasted words. Front-loads the core function and format options. Every sentence adds value.

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?

Given full schema coverage and helpful annotations, the description is largely complete. However, no output schema exists, and the description omits details on response structure (e.g., URL format, expiration). Could be slightly more informative.

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 describes all parameters (100% coverage). Description does not add new meaning beyond what the schema provides (e.g., does not explain how to find fileKey or ids, or scale effects). Baseline score of 3 is appropriate.

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 states it renders Figma nodes as image URLs for specified formats (PNG/JPG/SVG/PDF). However, the sibling tool 'export_node_as_image' may overlap in purpose, and the description does not distinguish itself, leaving potential ambiguity.

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?

Mentions the prerequisite FIGMA_TOKEN but provides no guidance on when to use this tool versus alternatives like 'export_node_as_image'. No exclusions or context for optimal use.

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