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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description still adds real behavioral detail the annotations cannot: the fixed 28-day lookback and the confirmation rule (drops require two consecutive measurements within 3 days, rises count immediately). It says nothing about result ordering or whether results are capped beyond limit.

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 run-on sentence strings together dozens of comma-separated field names with no grouping or bullets, making it hard to scan. The leading clause is well front-loaded, but the remainder reads as an undifferentiated data dump where related concepts (ads, shopping, mobile, opportunities) are not separated.

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?

No output schema exists, so enumerating return fields is legitimately necessary work, and the description covers ranking states, ad data, shopping, bid range, mobile position, intent, competition and opportunities. It is close to complete for a two-parameter read tool, with only ordering and pagination behavior unaddressed.

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 100% and both parameters are documented in the schema, including the limit default of 50 and the site_id provenance. The description adds no input-side meaning (neither site_id nor limit is mentioned), so the baseline 3 applies; its detail is entirely about returned fields.

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?

Opens with a specific verb and resource: 'List Search Console queries for a website over the last 28 days', then enumerates the tracked-keyword metrics returned. The read/list framing implicitly separates it from add_keywords, but no sibling is named explicitly, so differentiation relies on inference.

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 statement of when to call this versus get_pages, get_competitors, or get_site_metrics, and no prerequisites or exclusions. The only usage constraint conveyed is the fixed 28-day window, which is a scope fact rather than routing guidance.

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