create_rectangle

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

No annotations provided and the description gives no behavioral details. It doesn't disclose if creation triggers any side effects, requires authentication, or what coordinate system is used. This is a significant gap for a mutation 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?

The description is very concise (one sentence), which is front-loaded and efficient, but it is too brief to provide helpful context. It sacrifices substance for brevity, earning an average score.

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?

With no output schema, no annotations, and only a one-sentence description, the tool lacks essential completeness. It fails to explain the rectangle's placement on the canvas, coordinate system, or possible restrictions, leaving the agent underinformed.

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% with descriptions for all parameters, but the descriptions are minimal (e.g., 'X position') and add little beyond the parameter names. The description itself does not elaborate on parameter constraints or defaults, so baseline 3 is appropriate.

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 action (create) and the resource (rectangle) in Figma, distinguishing it from sibling tools like create_frame or create_text. However, it lacks specificity about the coordinate system or units, which is minor but prevents a perfect score.

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, no prerequisites, and no indication of required permissions or context. The description simply states the function without any usage context.

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