figma_write

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

With no annotations, description fully discloses sandbox execution, banned APIs, session state persistence, and return format {ok, result, logs, warnings}, ensuring transparency.

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?

Three sentences, no fluff, front-loaded with action, efficient and structured.

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 no output schema, description covers return values and key behaviors like sandbox restrictions and session persistence, making it 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 coverage 100%, description adds value by explaining code body usage, await figma examples, and sessionId role for state sharing, beyond schema definitions.

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 states 'Execute modern-ES JavaScript...to draw/modify the canvas', clearly indicating a write operation on the Figma canvas, distinct from sibling tools like figma_read.

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?

Provides context on when to use (draw/modify canvas), but does not explicitly exclude reading or mention alternatives; however, banned functions and session persistence are noted.

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