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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the description is not burdened with the safety profile. It adds genuinely new operational context: the required integration, the remediation URL, and how property resolution behaves across multiple connected Google accounts.

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-loads the definition, then use case, then prerequisite, then edge-case behavior on account ambiguity, in a few tight sentences. No redundancy with the schema or annotations.

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?

Covers the conceptual definition, the use case, the auth prerequisite, and multi-account routing — the things an agent needs before calling. It does not sketch the shape of returned rows (pages, impressions, CTR), which matters slightly given there is no output schema, leaving a minor gap.

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% and each of the 6 parameters (site, maxCtr, minImpressions, rowLimit, dates) is documented with defaults in the schema. The description adds no parameter-level meaning beyond that, 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+resource ('Find pages') plus the defining condition (high impressions, low CTR) and glosses the concept in plain terms. The 'pages' framing inherently separates it from the sibling get_gsc_low_ctr_queries, so an agent can route correctly.

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 usage context ('Good starting point for title/description rewrites') and states a hard prerequisite (Google Search Console must be connected). It does not name when *not* to use it or point at an alternative tool for adjacent needs, so it falls short of a 5.

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