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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds no behavior beyond that: it does not mention that results are capped (limit max 50 / default 20), whether matching is exact or normalized, or what happens when the pattern is unrecognized.

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?

Two short sentences, front-loaded with the core verb and resource, with examples placed early. The second sentence is a use-case hint that slightly duplicates the first rather than adding new constraints, but nothing is padded or confusing.

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 simple three-parameter read tool with a fully documented schema and complete annotations, this is adequate to call correctly. It is thin on what the agent should expect back — no mention of the default 20 / max 50 result cap, ordering, or whether an empty result means an invalid pattern — which matters for interpreting 'no vehicles' answers.

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 100%, so the schema already documents bolt_pattern format with its own example and explains limit's 1-50 range. The description's extra examples (5x114.3, 6x139.7) are mildly useful for supporting 5-lug and 6-lug variants, but it never mentions the optional make filter, so it adds little beyond the schema baseline.

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 a specific verb and resource ('List vehicles') scoped by a named identifier ('given bolt pattern') and supplies concrete format examples (5x114.3, 6x139.7). It does not distinguish the tool from the sibling lookup_wheel_fitment, which is the closest conceptual neighbor, so it falls short of a 5.

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 clause 'Useful to check which cars a wheel will bolt onto' implies a use case (wheel-fitment research) but gives no explicit when-to-use versus lookup_wheel_fitment or list_makes, and no exclusions or prerequisites. Usage must be inferred from the phrasing rather than stated.

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