web_search_multi

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

No annotations are provided, so the description carries the full burden. It discloses that searches are performed 'in sequence' and results are 'grouped by engine,' which is useful. However, it does not mention failure handling, rate limits, or other behavioral traits that could affect agent decisions.

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 extremely concise: two sentences (21 words) that front-load the core purpose in the first sentence and add detail in the second. Every word earns its place, with no redundancy or filler.

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?

An output schema exists but is not described. The description covers the basic workflow of multi-engine search and grouping but omits details like error behavior, pagination across engines, or impact of parameters like 'deep_mode'. For a tool with 8 parameters, it is minimally complete.

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 50%, but the description adds no additional parameter meaning beyond what the schema provides. Parameters like 'page', 'time_range', 'deep_mode', and 'deduplicate' remain unexplained in context of multi-engine search, leaving gaps for the agent.

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 searches multiple search engines and combines results. It uses the verb 'search' and resource 'multiple search engines,' and distinguishes from sibling 'web_search' (likely single engine) by specifying multi-engine and grouping.

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 implies when to use this tool (when you need results from multiple engines) but does not explicitly state when not to use it or mention alternatives. It provides enough context for an agent to differentiate it from siblings.

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