rhino_create_rectangle

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

Annotations indicate readOnlyHint=false and destructiveHint=false, aligning with the 'create' action. The description adds no behavioral nuance beyond stating the creation, such as side effects (e.g., returns object, modifies scene) or coordinate system implications. It does not contradict annotations.

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 sentence, 'Create a rectangle from origin, width, and height,' is concise, front-loaded with the primary action, and contains no superfluous words. Everything stated 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?

The description is adequate for a simple creation tool. It covers the core inputs and action. Missing details like the coordinate system or return value are less critical because the output schema exists and the operation is straightforward. Could mention orientation explicitly, but not a major gap.

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?

The schema already provides descriptions for width (Width (X direction)), height (Height (Y direction)), and origin (Corner origin point). The tool description mentions these but does not add new semantic meaning beyond what the schema describes. It reinforces the relationship but doesn't clarify anything missing.

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 states it creates a rectangle using origin, width, and height, which is clear and specific. 'Create a rectangle' is a precise verb-resource pair. It does not explicitly differentiate itself from other shape creation tools, though the tool name already does so, hence not a 5.

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?

There is no guidance on when to use this tool over alternatives, such as when a rectangle is needed versus other primitives, or any prerequisites like active layer context. The description only states the action 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.