get_query_page_stats

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'detailed traffic statistics' but doesn't specify what 'detailed' entails, such as metrics included, time ranges, or data formats. It also omits critical behavioral traits like permissions required, rate limits, or whether this is a read-only operation, which is essential for a tool with no annotations.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 complexity of traffic statistics tools, the description is minimal but not entirely inadequate. An output schema exists, so return values needn't be explained. However, with no annotations and low schema coverage, it lacks sufficient context for safe and effective use, such as behavioral constraints or parameter details, making it only partially complete.

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 0% description coverage, so the description must compensate. It mentions 'specific query' but doesn't clarify the parameters 'site_url' and 'query' beyond their names. No details are provided on expected formats (e.g., URL structure, query syntax), leaving semantics unclear and failing to address the schema gap.

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 action ('Get') and resource ('detailed traffic statistics for a specific query'), making the purpose understandable. However, it doesn't distinguish this tool from similar siblings like 'get_query_stats' or 'get_query_traffic_stats', which appear to handle related query statistics.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling tools for query and traffic statistics (e.g., 'get_query_stats', 'get_query_traffic_stats', 'get_query_page_detail_stats'), the description lacks context for selection, leaving the agent to infer based on names alone.

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