figma_get_component_image

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

Annotations already declare readOnlyHint=true, and the description adds 'context-safe', which aligns with read-only behavior. It also transparently states default format and quality. However, it does not disclose any side effects or limitations beyond what annotations provide.

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?

Two concise sentences: first covers purpose and output, second covers defaults and safety note. No unnecessary words or repetition.

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?

Specifies return format (base64 image) and node scope (component/frame), but lacks details on error handling, required permissions, or how the output should be processed. Given the tool has 4 parameters and no output schema, more context is needed for complete understanding.

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 has 0% description coverage, and the description only mentions defaults in passing ('Defaults to JPG@1x q70'). It does not explain the meaning or impact of parameters like nodeId, scale, format, or jpegQuality, leaving the agent without sufficient context to set them correctly.

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?

Clearly states action ('Get screenshot') and resource ('node (component/frame)'), with specific output ('Returns base64 image'). Distinguishes from sibling tools like figma_export_nodes by focusing on a single node screenshot.

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?

No explicit guidance on when to use this tool vs alternatives like figma_export_nodes or figma_capture_screenshot. The phrase 'v1.8.0 context-safe' is ambiguous and does not clarify usage context.

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