rhino_axis_ribs

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

Annotations already indicate readOnlyHint=false, so the description adds minimal behavioral context beyond 'generate'. It does not mention side effects, undo behavior, or performance, but it does specify the output is 'section ribs'.

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, focused sentence that conveys the core purpose and a key constraint ('bridge only') with no wasted words.

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?

For a tool with 7 parameters and an output schema, the description is too minimal. It omits details like what the generated ribs are (curves, geometry) and how parameters affect the output. The existence of an output schema partially compensates, but the description could be more informative.

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 description adds no parameter information. Several parameters (layer, count_a, count_b) lack descriptions in the schema. The description could clarify their role but does not.

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 'generate two orthogonal sets of section ribs' with specific qualifiers ('waffle-style fabrication, bridge only'), providing a distinct purpose that differentiates it from siblings like rhino_section or rhino_contour.

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 phrase 'bridge only' hints at a specific use case, but there is no explicit guidance on when to use this tool versus alternatives (e.g., rhino_section_at_axis) or when not to use it.

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