search_google

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It only says the tool searches through hosted providers; it does not disclose provider fallback behavior, merging semantics, rate limits, or failure modes despite having a provider enum and max_total_results parameter.

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 front-loaded sentence with no filler or repetition. However, 'configured hosted providers' is somewhat jargon-heavy and could be clearer without adding length.

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?

With no output schema and no annotations, the description should explain what the agent receives, how providers affect results, and when this tool is appropriate. It does none of that, and the large sibling list makes the missing routing guidance more consequential.

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 80%, and parameters like num_results, safe_search, and max_total_results already have meaningful schema descriptions. The description adds only the 'configured hosted providers' context, which is not parameter-specific; this is a baseline-3 situation where the schema does most of the work.

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 names a specific verb ('Search'), resource ('Google'), and mechanism ('configured hosted providers'), making the basic function clear. It does not explicitly distinguish this from sibling tools like search_web or search_google, so it loses the top score.

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?

No guidance is given on when to use search_google versus siblings such as search_web, search_news, or list_providers. The phrase 'configured hosted providers' hints at prerequisites but does not explain setup or selection criteria.

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