search_console_analytics_top_pages

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

No annotations are provided, so the description bears the full burden. It states it is a shortcut for analytics.query, implying a read operation. However, it does not disclose behavioral traits such as authentication needs, rate limits, or data freshness. The description adds moderate value beyond the tool 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 extremely concise with only two sentences, no fluff. Every word adds value: the first states the purpose, the second provides context about its relationship to analytics.query.

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?

Given the tool's simplicity and the absence of an output schema, the description could benefit from mentioning what the output contains (e.g., pages with metrics). However, the reference to analytics.query partially compensates. It is mostly complete for a straightforward convenience tool.

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?

The input schema already covers all 4 parameters with descriptions (100% coverage). The description does not add any additional meaning beyond what the schema provides. Baseline score of 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 clearly states 'Get top pages for a site' and distinguishes this tool from the generic analytics.query by noting it's a shortcut with specific dimensions. This provides a specific verb and resource, and differentiates from siblings like search_console_analytics_query.

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 indicates this tool is a shortcut for analytics.query with dimensions=['page'], implying it should be used when the goal is to retrieve top pages. However, it does not explicitly state when not to use it or provide alternative scenarios, but the context is clear enough.

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