get_query_traffic_stats

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

There are no annotations, so the description carries the burden of disclosing behavior. It does state that the tool returns a list of traffic statistics and raises BingWebmasterError on failure. It misses broader context such as site verification requirements, permission needs, or other behavioral constraints, but for a read-only 'get' tool this is a minimally workable disclosure.

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 compact and structured with clear Args, Returns, and Raises sections. It contains no filler or redundant restatement of the schema, and the one-line summary is sufficient to convey the tool's core function.

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 is simple, has only two parameters, and has an output schema, so the description does not need to explain return shapes in detail. It is still not fully complete because it fails to position the tool among its many query-statistics siblings and omits conditions like site verification or prerequisites.

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 this description is the only source of parameter meaning. It defines site_url as the URL of the site and query as the search query, which is enough for agents to understand the two required parameters, even though it adds no format, size, or constraint information.

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 scope: getting detailed traffic statistics for a specific query. However, it does not distinguish itself from closely related sibling tools such as get_query_stats, get_query_page_stats, or get_rank_and_traffic_stats, which leaves some ambiguity for tool selection.

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 a summary and mentions arg names, but it gives no guidance about when to choose this tool over similar query-statistics tools. It also notes no exclusions, prerequisites, or alternatives, so an agent has to infer the right choice from the name alone.

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