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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds a behavioral prerequisite (GSC must be connected) and directs the user to an integration page, which is valuable context beyond annotations. No contradictions detected.

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 four short, purposeful sentences. It front-loads the core purpose, then adds a use-case clarification and a setup requirement. No fluff or redundancy; every sentence earns its place.

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?

For a read-only tool with rich annotations and 100% schema coverage, the description covers purpose, use case, and a key prerequisite (GSC connection). It does not explain return format or pagination, but the schema and annotations provide enough context for an agent to select and invoke the tool correctly.

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 documents all 5 parameters fully. The description adds no additional parameter-level meaning beyond what is already in the schema, so 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 states a specific action and resource: 'Get search queries driving traffic to a specific page.' This clearly distinguishes it from sibling tools like get_gsc_top_queries (which returns top queries across a site) and get_gsc_query_pages (which returns pages for a query). The phrase 'what a page ranks for' adds clarity.

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 provides clear context: it is useful for understanding a page's ranking queries. However, it does not explicitly mention when not to use it or name alternative sibling tools, so it lacks exclusion guidance. The prerequisite about requiring GSC connection is helpful for usage.

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