get_query_page_stats

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Get' implies a read operation, but the description does not mention return behavior, time-range semantics, required permissions, or any other operational characteristics. It adds little beyond the tool name and title.

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, front-loaded sentence with no wasted words. It is concise, though it achieves this by omitting almost all usage and parameter detail.

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?

Despite having an output schema and only two simple parameters, the description is insufficient given the large, confusing sibling set. An agent cannot reliably select this tool over get_query_traffic_stats or get_query_page_detail_stats, and cannot understand the input parameters from the description.

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 0%, and the description does not explain either parameter. It only implies the query parameter is the focus, leaving site_url completely unaddressed and failing to clarify the type or format of 'query' or 'site_url.'

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 states a clear action and subject: 'Get detailed traffic statistics for a specific query.' It is clear in isolation, but it does not differentiate from closely named siblings like get_query_traffic_stats, get_query_page_detail_stats, or get_page_query_stats, all of which sound nearly identical.

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 gives no guidance on when to use this tool versus the many similar siblings. It implies a use case (wanting traffic stats for a query) but provides no context, exclusions, or alternatives.

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