get_query_traffic_stats

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

With no annotations, the description must fully disclose behavior, but it only mentions return type and possible exception. It does not cover side effects, permissions, rate limits, or the significance of the 'self' parameter, which is required but not explained.

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 short and follows a clear structure (Args, Returns, Raises). It is concise, though the omission of the 'self' parameter detracts slightly from completeness.

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 siblings and lack of annotations, the description is incomplete. It does not help distinguish from other query statistic tools, and fails to explain a required parameter. The presence of an output schema is noted but does not compensate for missing context.

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%, so the description must compensate. It describes 'site_url' and 'query' briefly but omits the required 'self' parameter entirely. No additional details on format, constraints, or usage are provided.

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 retrieves 'detailed traffic statistics for a specific query', providing a specific verb and resource. However, it does not differentiate from closely related siblings like 'get_rank_and_traffic_stats', which also deals with traffic statistics for 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?

No guidance is provided on when to use this tool versus alternatives such as 'get_rank_and_traffic_stats' or 'get_query_stats'. There is no mention of prerequisites, context, or scenarios where this tool is preferred.

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