Search (user-initiated only)

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

The description says 'can be called freely without user initiation' yet the annotation title says 'user-initiated only' – a direct contradiction that misleads the agent about when the tool can be invoked. This is an annotation contradiction.

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 concise, front-loaded with the core purpose, and each of its four sentences adds functional detail or usage nuance. There is no filler or redundancy.

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?

The description covers the tool's purpose, example usage, parameter tuning, and invocation policy. Combined with an output schema and 100% parameter schema coverage, it is fairly complete, though it does not address edge cases or provide explicit alternatives among siblings.

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 covers all 8 parameters, but the description adds meaningful semantics by explaining the plus/minus concept and specifically advising to tighten do_max for 'without changing the overall diameter' requests, which goes beyond the schema's raw limits.

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 clearly states it 'Calculate plus/minus sizing alternatives for a wheel/tire combo' – a specific verb and resource. This distinguishes it from sibling search/check tools and effectively communicates the tool's core function.

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 explains the use case ('Given OEM wheel specs...') and provides guidance on parameter tuning ('Tighten do_max...'). It also notes it can be called freely without user initiation, but does not explicitly contrast with sibling tools or state when not to use it.

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