Gear: Section A-A View

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

Annotations only include destructiveHint=false, leaving behavior mostly to the description. The description adds value by stating 'Deterministic' and listing included elements, but does not disclose return format, side effects, or resource requirements beyond the annotation.

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 two sentences, front-loaded with the core purpose, and every sentence adds value. No redundancy or fluff.

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?

Given the tool outputs a complex section view, the description adequately lists content but lacks details on parameters' effect on output, the section cut location (A-A), and return behavior despite having an output schema. Adequate but not fully complete.

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%, and all parameters have descriptions. The description does not add extra meaning beyond the schema beyond clarifying gear_metadata as the return from front view tools, which is already in the schema description. 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 tool creates a 'side cross-section' of a gear, specifying it is deterministic and lists included elements (boundaries, bore lines, keyway notch, hatch). It distinguishes from siblings by referencing gear_draw_*_front_view, but could be more explicit with a verb like 'draws' or 'creates'.

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 implies usage context by stating it applies to gears created by gear_draw_*_front_view, setting a prerequisite. However, it does not provide when-not-to-use guidance or compare with similar sibling tools like keyway_draw_section.

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