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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful non-schema behavior: the integration prerequisite, the setup path, and account-resolution logic when multiple Google accounts exist. It omits result format and whether rowLimit is enforced before or after aggregation.

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?

Three sentences, each doing distinct work: what it returns, the prerequisite with an actionable URL, and the multi-account edge case. Purpose is front-loaded with no filler.

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 compensates by enumerating the returned metrics (impressions, CTR, average position) and the sort dimension. Combined with the auth prerequisite and account handling, an agent has everything needed to call this correctly and to explain failures.

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%, so the schema already documents all five parameters including defaults and the rowLimit max. The description adds only that results are ordered by clicks, which is ordering rather than a parameter, so baseline 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 and resource ('Get the top pages on a site') plus the exact metric basis ('by clicks from Google Search') and the returned metrics. This distinguishes it from generic sibling get_top_pages and from get_gsc_top_queries, though no sibling is explicitly named.

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?

Gives clear context for use: Google Search Console must be connected, and it names the exact URL to send users to for setup. It also resolves the multi-account ambiguity (the property is read through whichever account can see it). It does not, however, say when to prefer this over siblings like get_top_pages or get_gsc_page_queries.

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