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

Annotations already declare the safe read-only/idempotent/open-world profile, so the bar is lower, yet the description adds real operational context: each call consumes one lookup from the plan's allowance (quota cost) and results are live/fresh so repeated calls for the same keyword are wasteful. Note the idempotentHint refers to no side effects, not identical output, so 'live results' is not a contradiction.

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?

Two sentences that are front-loaded with the core purpose and return shape, followed by the site trick and the quota/repeat caveat. Efficient with no filler, though the second sentence is dense with multiple ideas packed together.

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?

There is no output schema, but the description fully describes the return payload (organic results fields plus additional page elements), the optional 'site' enrichment, and the quota/repeat constraint. Nothing essential for calling it correctly is missing.

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 83%, so the schema already documents most parameters (baseline 3). The description adds meaning beyond the schema: it ties 'site' to rank-marking ('where the user's site ranks and who is above it') and frames device/location as scope selectors for the SERP, which enriches the otherwise terse schema entries.

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+resource (live Google SERP for a keyword) scoped by country and device, and enumerates the exact return contents (organic results with position/domain/title/description plus AI overview, featured snippet, PAA, etc.). No sibling tool (bing_keywords, keyword_volume, gsc_*) does a live Google SERP pull, so the agent can distinguish it immediately.

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?

Gives actionable conditions: pass 'site' to see where the user's domain ranks and who is above it, and warns not to call repeatedly for the same keyword in one chat because results are live. It lacks an explicit named alternative tool to route to, but the when-to-use and when-not-to-call guidance is clear.

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