Search several things at once

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

Beyond the readOnly and openWorld annotations, the description discloses substantive behavior: ranking pads results, extra query words are ANDed, truncated groups cannot answer cheapest/only/none questions, and prices/availability depend on delivery location, with pointers to get_location and set_location. No contradiction with annotations.

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, each earning its place: main purpose first, then per-group behavior and caveats, then location context. There is no filler or repetition of schema details.

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 still tells the agent results are grouped by query and that each group carries its own coverage sentence. It also covers ranking, truncation, AND semantics, and location dependence, making the tool safely callable without missing critical context.

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 baseline is 3. The description adds extra meaning by explaining how queries are interpreted (extra words ANDed) and that truncated results affect question-answering, which enriches the queries and resultsPerQuery parameters beyond 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 uses a specific verb and resource: 'Run several catalogue searches in one call and get the results grouped by query.' This clearly distinguishes the tool from the single-query search_products sibling and matches the title's promise of searching several things at once.

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 first sentence states the batching rationale — 'so finding many products costs one round trip' — making it clear the tool is for multiple searches. It references search_products for caveats but does not explicitly say 'use search_products for a single query,' so the guidance is strong but not fully explicit.

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