web_search

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

No annotations are present, so the description carries the full burden. It does disclose that results are 'ranked' and include title, URL, and snippet, which is useful. However, it omits behavioral details like pagination, rate limits, or the effect of parameters like safesearch and region on the output.

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 a single sentence that is front-loaded with the action and result, containing no filler or redundant information. Every word contributes to understanding the tool's core purpose.

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?

While an output schema exists, the tool has five parameters with no usage explanations, no annotation-backed safety context, and no guidance on when to use it relative to siblings. The description covers only the basic purpose and leaves significant gaps for an AI agent trying to invoke it correctly.

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 0%, and the description provides no explanation of any of the five parameters (query, region, timelimit, safesearch, max_results). It fails to compensate for the schema's lack of descriptions, leaving parameter meanings entirely undocumented.

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 the specific verb 'Search' with the resource 'the web', and clearly states the output format: 'ranked title, URL, and snippet results'. This distinguishes it from sibling tools like web_scrape, which likely fetch a specific page rather than perform a 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 implies use for general web search but gives no explicit guidance on when to use this tool versus alternatives such as web_scrape or yt_info. There is no mention of exclusions or when a different tool would be more appropriate.

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