figma_create_rectangle

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

With no annotations, the description bears full weight but only states 'create' (mutation) without disclosing side effects, required permissions, or behavior like whether the rectangle is selected after creation. It adds minimal behavioral context beyond the obvious.

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?

A single, front-loaded sentence that delivers the core purpose without extraneous words. Every word earns its place.

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 having 8 parameters and no output schema or annotations, the description provides no information about return values, default behavior, error conditions, or interactions with the Figma page. It is severely incomplete for an agent to use effectively.

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 description coverage is only 25% (only fillColor has a description). The description does not explain any parameters, defaults, or their relationships, leaving agents to infer meanings from schema names alone.

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 'Create a new rectangle node on the current page,' specifying the action (create), resource (rectangle node), and location (current page). This distinguishes it from sibling tools like figma_create_frame or figma_create_text.

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 guidance on when to use this tool versus alternatives like figma_create_frame or figma_create_text. There is no mention of prerequisites, context, or scenarios where this tool is inappropriate.

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