search_console_analytics_top_pages

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states the purpose and does not mention that the tool is read-only, any rate limits, or the default row_limit behavior. This is minimal transparency for a data-retrieval tool.

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, consisting of only two short, clear sentences. Every word adds value – the first sentence states the purpose, the second explains the relationship to another tool. No unnecessary or redundant information.

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 has 4 parameters (3 required) and no output schema, the description does not cover the return format, pagination, or the default value for row_limit. While the purpose is clear, these omissions leave gaps in fully understanding the tool's behavior and output.

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?

All parameters have descriptions in the input schema (100% coverage), so the schema already documents parameter meaning. The description does not add additional context or constraints beyond what the schema provides, resulting in a baseline score of 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 that the tool retrieves 'top pages for a site' and distinguishes itself from sibling tools like 'analytics.query' by specifying it is a shortcut with dimensions set to ['page']. This provides a specific verb and resource, and sets it apart from similar tools such as 'search_console_analytics_top_queries'.

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 explains that the tool is a shortcut for 'analytics.query' with specific dimensions, implying it should be used when top pages are needed. However, it does not explicitly state when not to use it or provide alternative tools, so it lacks explicit exclusions but offers clear context.

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