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

Annotations already cover safety (readOnly, idempotent, openWorld, non-destructive), so the bar is lower, and the description adds real value: an auth dependency, a recovery URL for the unconnected case, and multi-account resolution behavior. It stops short of disclosing pagination/rowLimit behavior or rate limits, which keeps it from a 5.

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?

Front-loaded with the core purpose and return metrics, then the prerequisite, then the fallback instruction. Four sentences with little waste, though the final multi-account sentence is a mild tangent that only helps in a narrow edge case.

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 enumerates the returned fields (clicks, impressions, CTR, average position) and covers the auth/setup gap that would otherwise block a call. What's missing is guidance on rowLimit/default sizing and how results are ordered beyond 'by clicks'.

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%, so every parameter is documented in the schema including the searchType enum caveat about discover/googleNews. The description's mention of 'ordered by clicks' and the returned metrics adds a little framing but no parameter-level detail beyond the schema. Baseline 3 is appropriate.

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 gives a specific verb and resource ('Get the top search queries driving traffic to a site, ordered by clicks') and names the four metrics returned, so an agent can tell it apart from page-oriented siblings like get_gsc_top_pages. It stops short of explicitly naming the sibling tools that offer overlapping query data (get_gsc_query_trend, get_gsc_page_queries), so it's differentiation-by-implication rather than explicit.

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?

The description states a prerequisite (Search Console must be connected) and a remediation URL, which is useful operational guidance. But it never says when to prefer this over get_gsc_query_trend, get_gsc_opportunity_queries, or get_gsc_low_ctr_queries, so the agent must infer the choice from the tool names alone.

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