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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that results include clicks, impressions, CTR, and average position per query, which gives some behavioral context, but it does not mention grouping/sort semantics, date-window behavior, row-limit effects, or response shape.

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 a single front-loaded sentence with no filler or repetition. Every word contributes to the core purpose, which is exactly what this dimension rewards.

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 and only 20% schema parameter coverage, the description carries a heavy burden that it does not meet. It omits necessary context about required date ranges, what 'top' means, how type affects results, and what output to expect, leaving a 5-parameter tool under-specified.

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 only 20% (site_url only), yet the description adds no parameter-level meaning for start_date, end_date, type, or row_limit. 'For a property' and 'by clicks...' do not compensate for the missing date-range and type semantics, so an agent must infer key meanings from names and patterns.

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 clearly names the resource (top queries) and metric dimensions (clicks, impressions, CTR, average position), so an agent can tell it targets query-level GSC data. It does not explicitly differentiate it from siblings like get_gsc_page_queries or query_gsc_search_analytics, 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?

There is no guidance on when to prefer this tool over get_gsc_page_queries, get_gsc_top_pages, or query_gsc_search_analytics, nor any exclusions or prerequisites. The only usage signal is the phrase 'top queries,' which essentially restates the tool's name.

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