search_web_pages

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

Annotations already readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds behavioral traits: returns snippets, supports two modes (pro/realtime), and provides query tips. 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?

Approximately 100 words, well-structured with clear paragraphs for purpose, tips, and filtering/modes. Every sentence adds value; no fluff.

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 7 parameters, 1 required, rich annotations, and no output schema, the description covers usage tips, parameter explanations, and modes. Lacks details on result structure (only mentions 'snippets') but is otherwise comprehensive.

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?

With 100% schema description coverage, baseline is 3. Description adds significant value beyond schema by explaining query strategy (semantic descriptions), purpose of filters, and mode selection, enriching understanding.

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 is a web search tool for current events and recent data, distinguishes from sibling 'fetch_page_content' by positioning itself as the default search tool, and specifies that it returns snippets.

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?

Provides explicit guidance on when to use (current events, data beyond cutoff), query tips (describe ideal page, not keywords), and how to narrow results using date and site filters and two modes. Lacks explicit when-not-to-use scenarios but is otherwise clear.

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