gsc_top_pages

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds that results are ordered by highest clicks, but does not disclose that the default dimensions setting is 'query', which may return queries rather than pages unless overridden—a potential mismatch with the tool's name.

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 sentence that directly conveys the core functionality with no filler words. It is well-structured and immediately understandable.

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 tool with 10 parameters, no output schema, and minimal schema descriptions, this description is inadequate. It omits any mention of pagination, default limits, dimension handling, or how the results are returned. The simple sentence does not provide enough context for an agent to use the tool effectively, especially given the lack of schema guidance.

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 10% (only siteUrl has a description). The description does not explain any parameters, such as limit, dimensions, filters, or dataState. Since schema coverage is low, the description should compensate, but it remains silent on parameter meaning or defaults.

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 states the action ('Return'), the resource ('highest-clicked pages'), and the scope ('for a date range'). It distinguishes from gsc_top_queries which focuses on queries, but does not explicitly differentiate from gsc_query_pages, which also returns pages.

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?

Provides no guidance on when to use this tool versus alternatives like gsc_query_pages or gsc_top_queries. No prerequisites, exclusions, or context for choosing this tool are mentioned.

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