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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds value beyond that: it discloses the data is bounded by 'the dataset' and explicitly labels torque ranges as 'guidance only', a meaningful caveat for an agent relaying safety-relevant numbers to a user.

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?

Front-loaded with 'Use for' followed by four high-signal example queries, then a compact enumeration of outputs. It is one dense sentence that stays readable, though the example-query list is long enough that a reader must parse it fully to reach the capability list.

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 an output schema present, return values need not be explained, and the description covers inputs, outputs, and safety caveats adequately for a single-parameter read tool. The main omission is routing guidance against the near-duplicate sibling bolt_pattern_lookup, which an agent would need to choose 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 coverage is 100% and the pattern parameter already carries format examples (5x114.3, 5x4.5, 6x139.7, 8x6.5). The description restates that both mm and inch notation are accepted but adds no syntax, normalization, or parsing rules beyond the schema. Baseline 3 applies.

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?

States specific verbs and resources: unit conversion of bolt patterns, look-alike listings, vehicle membership, lug tightening order, and torque ranges. An agent knows exactly what comes back. It does not, however, distinguish itself from the sibling 'bolt_pattern_lookup', which sounds like it covers overlapping ground.

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 quoted example queries ("what is 5x114.3 in inches", "is 5x114.3 the same as 5x115", "will 6x135 wheels fit 6x139.7", "which vehicles use a pattern") give concrete triggering contexts that map directly onto user intent. No explicit exclusions or named alternatives are given, and the overlap with bolt_pattern_lookup and wheel_fitment_check is left unresolved.

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