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

The description frames this as a passive read ('Retrieve'), but the annotations declare readOnlyHint=false and idempotentHint=false, implying the call may change state — a mismatch an agent has to resolve on its own. With annotations present the bar is low, yet the description adds no behavioral context (auth/account requirements, result caching, empty-result behavior) to offset the conflict.

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?

A single sentence with the core action and resource front-loaded, so it reads quickly. The trailing 'actionable SEO content opportunities' is vague marketing phrasing that hints at return fields but doesn't add callable information.

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, the description usefully names return fields (impressions, clicks, average position, opportunities), which is genuine added value. However, for a data-retrieval tool it omits how the site is resolved, whether results are sorted by clicks, and how the days/limit interact, so it is adequate but not complete.

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% with defaults for days (28), limit (15), and bounds, so the schema already carries the parameter semantics. The description adds no extra meaning about the lookback window, the 50-row cap, or what omitting siteUrl does, so the baseline of 3 applies.

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 (Retrieve) and resource (top search keywords/queries driving organic Search impressions and clicks), which is clearly distinct from sibling reads like google_search_console_get_top_pages or get_performance. It never names those siblings, so the differentiation comes from the resource noun rather than explicit contrast, keeping it 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?

There is no when-to-use guidance, no prerequisites (e.g., that a Google Search Console property must be connected), and no mention of alternatives such as get_performance for a broader breakdown or get_top_pages for page-level data. The agent must infer the selection criteria entirely.

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