get_query_traffic_stats

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states that this is a read-style 'Get' operation. It does not clarify what traffic metrics are included, how 'over time' is aggregated, or any limitations, leaving only the phrase 'over time' as a behavioral clue.

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 filler or redundancy. It is appropriately concise, even though it under-delivers on 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?

The tool has an output schema, but it has no annotations, 0% schema parameter documentation, and many similarly named sibling tools. The description does not specify the exact metrics, the period syntax, or how site_url scopes the query, so it is not complete enough for confident selection and correct invocation.

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 parameter description coverage is 0%, so the description needed to compensate for the missing parameter documentation. It weakly maps 'queries' to the query parameter and 'over time' to period, but it does not explain site_url, the expected period format, or the meaning of the returned statistics.

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 identifies a specific verb ('Get'), resource ('traffic statistics'), and scope ('for queries over time'), so the core function is clear. However, it does not distinguish this tool from siblings like get_query_stats or get_query_page_stats, so it falls short of a 5.

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 no guidance on when to use this tool instead of the many similar sibling tools. It offers no exclusions, prerequisites, or alternative routing, leaving the agent to guess based on the name alone.

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