calculate_thread_tap

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds that this is a pure calculation tool producing tap drill, RPM, and feed, but it does not mention assumptions, unit expectations, or how constraints like threadPercent are applied.

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 a single sentence with the verb and resource front-loaded, and it wastes no words. The ambiguous 'grounded' is a minor clarity issue, but structurally the description is appropriately compact.

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 six parameters, a nested geometry object, enums, defaults, and numeric constraints, the one-line description leaves too much to inference. The output schema covers return values, but input semantics, required geometry subfields, and calculation assumptions are under-specified.

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%, so the description needs to compensate, but it only loosely maps 'metric or unified' to the system parameter and 'supplied geometry' to the geometry object. It does not explain threadPercent, tapType, cuttingSpeed, or the relationships among pitch, tpi, callout, and nominalDiameter, leaving most parameter semantics to the agent's inference.

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 states a specific verb ('Calculate'), a clear resource ('thread/tapping geometry'), and the scope ('metric or unified'), while also naming the expected outputs: tap drill, RPM, and feed. The word 'grounded' is ambiguous, but the overall purpose is clear and distinguishes this from the other inspection and planning tools in the sibling list.

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?

Usage is implied by the description: an agent should call this when it has supplied geometry and needs thread/tapping calculations. However, there are no explicit when-to-use or when-not-to-use conditions, and no alternative tools are named, leaving the decision to inference rather than direct guidance.

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