Get Figma design (simplified)

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

No annotations provided, but the description details what the tool returns (tree, styles, hints, Tailwind classes) and mentions token-saving features like outline format and pruning. It transparently describes its non-destructive fetch behavior.

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: the first states the core function, the second gives usage guidance. No unnecessary words; front-loaded with the key verb 'Fetch'.

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 lacking an output schema, the description sufficiently explains the output (tree with layout, style, hints, Tailwind). It positions the tool as the initial step in a Figma-to-React workflow, which is complete for its role.

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 coverage is 100%, but the description adds significant value beyond schema definitions, e.g., explaining format trade-offs (outline vs JSON), the purpose of pruning wrappers, and the token-saving benefit of collapsing repeats.

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?

The description clearly states the tool fetches a Figma file/node and returns a compact LLM-friendly tree with layout, style, and Tailwind classes. It differentiates itself by being the first step before generating React code.

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 says 'Use this FIRST before generating any React code,' providing clear when-to-use guidance. It does not list alternatives but the context implies it as a prerequisite.

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