Google Search

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

With annotations already marking readOnlyHint and openWorldHint, the description adds essential operational details: results cached for 24h, environment variable to bypass cache, provider fallback logic, and no API key requirement for the default browser provider. 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?

The description is compact, front-loaded with the primary action, and every sentence delivers operational value (provider, return fields, cache, limits, auth). No unnecessary 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?

For a simple search tool with a small schema and output schema, the description covers all essential aspects: provider selection, caching and bypass, authentication, return fields, and limits. No major gaps in operational 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?

The schema already provides full descriptions for both parameters, including default/max limit and query search operators. The description only reiterates the default limit and max, adding minimal value 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 clearly states it performs a single Google search and specifies the return fields (title, URL, snippet). It distinguishes itself from sibling tools like search_parallel by emphasizing 'single' and from scholar_search by being a general Google 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?

Provides clear context on when to use it, including default provider, caching behavior, and the cache-bypass instruction for breaking queries. However, it does not explicitly mention alternatives or state when not to use it versus siblings like search_parallel or scholar_search.

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