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

The description frames the tool as a read/report operation that returns SERP data, but annotations declare readOnlyHint=false and destructiveHint=true. Because this creates a direct behavioral conflict and the description does not explain any destructive effect, it contradicts the 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 front-loaded with the core action, then return contents, usage, and cost. It is short and every sentence adds useful information without padding.

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?

An output schema exists, so return values need not be explained, and the description does cover output and cost. However, with 0% parameter description coverage and an unresolved annotation contradiction, it is not complete enough for reliable invocation.

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 0% across five parameters, and the description only mentions the keyword parameter. It gives no meaning for depth, refresh, language, or location, leaving most invocation semantics undocumented.

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 states a specific verb and resource: live SERP analysis for a keyword, returning Google top results with ranking, titles/domains/URLs, ratings, and paid-ad flags. It does not explicitly differentiate from the many SEO siblings such as seo_paid_keywords or seo_rank_tracker, so it stops short of a 5.

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 gives clear usage context: organic competitor analysis and ad-competition intel, plus a credit-cost warning. It does not name alternatives or when-not-to-use conditions, so it is not fully routing.

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