figma_docs

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

No annotations; description covers tool behavior (returns docs, read-only nature assumed). Missing explicit statement of no side effects, but clear for a documentation tool.

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?

Front-loaded with main purpose, structured with bullet-like list. Slightly long but well-organized and clear.

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?

Complete for a docs retrieval tool: explains purpose, usage, parameter options, and integrates guidance. No output schema needed.

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 100% coverage with enum and description; description adds rich context for each section value, e.g., what 'rules' contains.

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 it returns API reference and design rules for figma_write, distinguishes from sibling tools (figma_read, figma_write) by being a documentation tool.

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?

Explicitly instructs to call before any figma_write code, advises to call with no args first, then specific sections, and provides context for each section's usage.

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