Gear: Helical Front View

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

Annotations only provide destructiveHint=false. The description adds that the tool is 'deterministic' and returns a handle bundle plus metadata, indicating output behavior. However, it does not disclose whether it creates new entities in the drawing, required permissions, or any side effects beyond the return.

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 with no redundant words. It front-loads the tool's purpose and key output, then efficiently mentions optional features and downstream use. Every sentence serves a clear function.

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 complexity (10 params) and presence of an output schema, the description covers the tool's purpose, output structure, and relation to a sibling. Missing elements include prerequisites (e.g., active drawing) and error handling, but overall it is adequate for selection and invocation.

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?

With 80% schema coverage, the description adds value by grouping optional features: 'optional bore + keyway' and explaining output details like '40 pts/flank' and circle types. This helps the agent understand how parameters like bore_diameter and keyway_depth relate to the overall output.

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 it produces a 'helical gear front view' with specific elements like involute outline, circles, helix symbol, and optional bore/keyway. It distinguishes from the sibling 'gear_draw_spur_front_view' by specifying 'helical', though the description itself does not explicitly contrast them.

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 explicit guidance on when to use this tool versus alternatives like 'gear_draw_spur_front_view' or 'gear_draw_section_aa'. The description only mentions that it returns data for downstream 'gear_draw_section_aa', but does not state prerequisites or conditions for selection.

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