rhino_spiral

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

Annotations already indicate non-read-only (write). The description adds no further behavioral context: no side effects, auth needs, or limitations. It only implies creation.

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?

Extremely concise (one sentence), but too terse for a tool with complex nested parameters. Lacks structure: no bullet points or parameter overview. Front-loading is good, but content is insufficient.

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 many parameters (center, radii, pitch, turns, etc.) and a nested input schema, the description fails to cover key aspects. Output schema exists but not shown. Incomplete for an agent to use correctly.

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 0%, meaning the tool description does not explain any parameters. The schema itself has descriptions, but the tool description fails to add value or clarify parameter meaning. Agent must rely solely on schema.

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 verb 'Add' and the resource 'tapered spiral', and specifies the output type 'NURBS curve'. It distinguishes from sibling tools like rhino_helix by using 'tapered', but could be more precise about the 'sampled into' process.

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 (e.g., rhino_helix for non-tapered spirals). No mention of prerequisites, use cases, or exclusions.

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