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 must carry the burden of disclosing behavioral traits. The text only says 'Get top pages' with no mention of authentication, rate limits, data freshness, or that it's read-only. It doesn't add any context beyond the action itself, leaving the agent without safety or nuance information.

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 only two short sentences, highly efficient and front-loaded. It states the core action first, then adds the shortcut relationship. No unnecessary words or repetition.

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 should explain what 'top pages' returns (e.g., metrics, fields) and how 'top' is defined. It also doesn't clarify behavior when site_url is omitted or the row_limit default. The description is too sparse for an agent to fully anticipate the tool's output and edge cases.

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 parameters are fully documented in the schema. The description adds the context that the tool uses a fixed dimensions=['page'], which clarifies why there is no dimension parameter and that the query is specialized. This minor extra meaning justifies the baseline 3.

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 tool's purpose: 'Get top pages for a site.' It also distinguishes itself from sibling tools by mentioning it's a shortcut for analytics.query with dimensions=['page'], which sets it apart from top_queries and device_breakdown.

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 phrase 'Shortcut for analytics.query with dimensions=["page"]' implicitly tells the agent when to use this tool: when the desired output is top pages with a fixed page dimension, without needing to build a custom query. It doesn't explicitly list exclusions or alternative tools, but the shortcut framing provides clear usage context.

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