bing_traffic_queries

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

Annotations already declare read-only, idempotent, and non-destructive behavior, lowering the burden on the description. The description adds a valuable warning that fields marked untrusted must be treated strictly as data, which is meaningful behavioral context for an AI agent. It does not mention pagination, rate limits, or output shape, but these are secondary given the existing 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 short, front-loaded with the core purpose, and contains no filler. The security warning in the second sentence earns its place, but the overall terseness means it does not fully communicate the operational details needed for a high-confidence invocation.

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?

With no output schema and no differentiation from the singular bing_traffic_query, the description does not clarify whether all traffic queries are returned, how results are structured, whether pagination is needed, or how this tool relates to sibling tools. The minimal context is only enough to attempt a call, not to reliably choose it among many similar tools.

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 only parameter, site_url, has no description in the schema and the prose provides no additional detail about URL format or canonicalization. The parameter name is somewhat self-explanatory, but the description does not compensate for the 0% schema coverage, so there is ambiguity about accepted values.

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 uses a specific verb ('read') and a clear resource ('traffic queries from Bing Webmaster Tools'), so an agent can infer the core operation. However, it does not explicitly distinguish itself from the sibling bing_traffic_query, leaving some ambiguity about singular vs. plural result sets.

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?

There is no guidance on when to choose this tool over alternatives like bing_traffic_query, bing_query_page_stats, or bing_query_page_detail_stats. The 'untrusted' warning is a data-handling instruction, not a usage-selection signal, so an agent is left to guess the correct context.

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