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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior the annotations cannot convey: cost ($0.004 per page, +$0.002 AI Overview surcharge) and a fixed 10 results per page. It stops short of describing rate limits or result truncation behavior.

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?

Front-loaded with purpose and return shape, and the pricing sentence earns its place. The middle sentence restates parameter capabilities already in the schema, which is the only wasted space in an otherwise tight description.

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 8 parameters, no output schema, and a mutation-free read operation, the description covers the essentials: what comes back, unit of pagination, targeting dimensions, and cost. It lacks only guidance on choosing among the many sibling search_* tools, which matters given the crowded namespace.

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 100%, so the schema already documents all 8 parameters including enums and defaults; baseline is 3. The description reinforces operator support and page size, but adds no syntax, format, or interaction detail beyond the schema (e.g. how pages interacts with billing).

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?

States a specific verb and resource ('Search the web through Google organic results') and scopes it to organic web results, which separates it from sibling tools like search_news, search_forums, and google_ai_mode. It also names the returned fields, so an agent knows what it gets without an output schema.

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?

It implies usage through capability statements (operators, geo/language/device targeting, time filter, AI Overview) but never says when to pick this over search_news, search_forums, or google_ai_mode. There are no exclusions or alternative-routing guidance, so selection is left to inference.

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