rhino_cmd_circle

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

No annotations are provided, so the description must carry the full burden. It only states it 'Draw a circle' and mentions the return dictionary, but does not disclose side effects like document modification, object creation, or undo behavior.

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 extremely concise, with no redundant wording. Every sentence provides essential information about the tool's purpose, parameters, and return value.

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 covers the primary parameters and return value, making it adequate for a basic circle-drawing operation. However, it lacks contextual details such as whether the circle is added to the active layer, any prerequisites, or how it relates to other curve-creation tools.

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?

Each parameter is described with its role: 'controller' as a RhinoController instance, 'cx, cy, cz' as world-space center coordinates, and 'radius' as the circle radius. This adds meaning beyond the bare titles, though units or defaults are not specified.

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 tool's function: 'Draw a circle by center and radius.' This provides a specific verb and resource. However, it does not explicitly differentiate from similar circle-related tools like 'rhino_circle', so the purpose is clear but not fully distinguished.

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 offers no guidance on when to use this tool versus alternative circle creation methods. It does not mention conditions or advantages, leaving the agent to infer usage context.

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