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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuine provenance detail: results come from manufacturer strings already in the catalogue, and it distinguishes verified sizes from 'stated max tire claims' and 'lift-only notes'. It still says nothing about empty-result behavior, coverage limits, or response shape.

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?

A single dense sentence with no filler, front-loading the returned data. It is slightly jargon-heavy ('lift-only notes', 'manufacturer strings already in the catalogue'), which costs a little readability.

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 no output schema, the description usefully enumerates the returned fields. But for a 4-parameter tool with three required vehicle identifiers and thin schema descriptions, it omits input semantics and any no-match or coverage caveats, leaving the picture incomplete.

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 only 25% — just the optional 'tire' token is documented in the schema. The description never explains the required year/make/model inputs or how the optional tire token interacts with them, so it fails to compensate for the coverage gap.

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 resource and return set: verified tire sizes, max tire claims, lift-only notes, and matching wheels. An agent can tell this is a tire/wheel fitment lookup distinct from generic part search, though it never explicitly contrasts itself with check_part_fit or find_parts_for_vehicle.

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?

There is no when-to-use statement, no prerequisite (e.g. that year/make/model are required), and no reference to any sibling tool. The agent must infer from the name alone when this beats check_part_fit or search_parts.

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