Search (user-initiated only)

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

The description discloses the user-initiated-only constraint and warns against autonomous loops, which is behavioral information beyond the annotations' readOnly/idempotent hints. It also describes the response structure (facets and summary) and how to use facets for refinement, providing useful behavioral context.

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 organized into clear sections with a main purpose, response explanation, important usage warning, and alternative tool mention. While it is relatively detailed, each part serves a distinct purpose and provides necessary guidance.

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?

Given the tool's complexity (14 parameters, output schema, sibling alternatives), the description covers the core functionality, response usage, and selection criteria. It adequately orients the agent to when and how to use the tool, and the output schema covers return details.

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?

The input schema already documents all 14 parameters with descriptions, so the baseline is 3. The description adds context by specifying that metric sizes are required and by explaining how facet values can be echoed as filters, which complements the schema.

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 the tool finds vehicles compatible with a given metric tire size, using a specific verb and resource. It explicitly distinguishes from sibling tools like ws_search_by_hf_tire for high-flotation tires, and the title indicates user-initiated search.

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 states this is a Search method that should only be called when a user explicitly requests a tire compatibility search, and warns against autonomous calls. It also names the alternative tool for high-flotation tires, providing clear when-to-use guidance.

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