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 carries the full burden. It only states the basic operation without disclosing behaviors such as authentication requirements, rate limits, error handling, or response format. For a data retrieval tool, this is insufficient for an agent to understand side effects or constraints.

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 consists of two very short, front-loaded sentences. The first sentence states the purpose, and the second provides relationship context. No redundancy or unnecessary information, making it highly concise and structured.

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 absence of an output schema, the description does not explain what data fields the tool returns (e.g., impressions, clicks, position). It also lacks details about default sorting, pagination, or date range behavior. While the tool is simple, more context would help an agent fully understand its capabilities.

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 has 100% description coverage for all 4 parameters (site_url, start_date, end_date, row_limit). The description does not add any additional context or format guidance beyond what the schema already provides. Baseline 3 is appropriate as the schema is self-documenting, but the description adds no extra semantic value.

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 explains this is a shortcut for analytics.query with specific dimensions, which distinguishes it from sibling tools like search_console_analytics_top_queries and search_console_analytics_query. The verb+resource combination is specific and unambiguous.

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 by mentioning it's a shortcut for analytics.query with dimensions=['page'], implying it should be used when only page-level data is needed. However, it lacks explicit when-not or exclusionary guidance compared to similar tools like top_queries or the general query.

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