list-hf-tire-overall-diameters

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

Annotations declare readOnlyHint=true and openWorldHint=true, and the description does not contradict them. It adds useful context about the imperial size format, 'all' scope, and optional region filtering, though it does not detail return shape or pagination behavior.

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?

Three sentences with the core action front-loaded. The imperial format explanation is relevant, and the use-case sentence is direct. The bit about pickup trucks and off-road vehicles is slightly extra but not bloated.

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 read-only list tool with one well-documented optional parameter and no output schema, the description covers purpose, units, optional filter, and downstream use. It could be more explicit about the return format, but this is a minor gap given the simplicity.

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%: the region parameter is described as 'Market region code (e.g. "usdm", "eudm"). Get codes from list-regions.' The description adds only 'optionally filtered', which is already inferable from the parameter being optional, so the baseline 3 is appropriate.

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 'List all overall diameter values (inches) for high-flotation (HF) tyres, optionally filtered by region' with a specific verb, resource, units, and optional scope. The HF qualifier clearly distinguishes it from sibling tools like list-rim-diameters and list-hf-tire-rim-diameters.

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 description explicitly says 'Use this to discover valid overall_diameter values for search-by-hf-tire', giving a clear downstream use case. However, it does not mention exclusions or directly compare to related list tools beyond the implicit naming distinction.

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