figma_create_rectangle

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

No annotations are provided, so the description must disclose behavioral traits, but it only states the action 'Create a rectangle'. It does not mention that the operation adds a new node to the document, what parent is used by default, coordinate units, or any side effects, leaving the agent completely uninformed.

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?

The description is concise but under-specified. It is a single sentence that essentially repeats the tool name, providing no value. It cannot be considered efficient since it fails to convey any useful information beyond the schema/name.

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?

Given 11 parameters, no annotations, and no output schema, a one-sentence description is severely incomplete. It should explain the rectangle's placement, default behavior, and parameter semantics, but instead leaves almost all context missing.

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?

With only 18% schema description coverage (fillColor, strokeColor), the description must compensate for the other 9 parameters, but it adds nothing. It does not explain required width/height, x/y coordinates, opacity, cornerRadius, strokeWeight, name, or parentId semantics, forcing the agent to guess.

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 'Create a rectangle' exactly restates the tool name (figma_create_rectangle) without adding any new information. While it identifies the verb and resource, it is tautological and does not provide any differentiation from sibling creation tools beyond the noun itself.

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?

The description provides no context about when to use this tool versus alternatives (e.g., figma_create_ellipse, figma_create_frame, figma_create_text). There are no exclusions, prerequisites, or references to alternative tools.

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