Google Search

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

Discloses caching behavior (24h), performance (first call ~4s, then ~2s), CAPTCHA handling, and env var alternatives. Annotations already indicate readOnlyHint=true, but description enriches with specific operational details. 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?

Extremely concise: one sentence per major idea. Front-loaded with purpose, then caching, performance, and edge cases. Every sentence is necessary and information-dense.

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 presence of an output schema (not shown) and only two simple parameters, the description covers all essential aspects: what it does, how to use, caching, performance, and error handling. It is complete for a search tool of this complexity.

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 coverage is 100% with descriptions for both parameters. The description adds valuable usage tips: 'Use site: filters and quotes for exact match' for the query parameter, reinforcing the schema. This extra context justifies a score above the baseline of 3.

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 'Single Google search -> title/url/snippet per result', using a specific verb and resource. It implicitly differentiates from siblings like search_parallel and search_extract through the word 'single'.

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 when-to-use: 'prefer re-querying over caching results yourself', and when to bypass cache: 'for latest/today/breaking queries set SURF_CACHE_TTL_SEARCH_MS=0'. Also mentions CAPTCHA handling and cloud mode as alternatives. Clearly guides agent behavior.

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