bing_rank_traffic_stats

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

No annotations are provided, so the description carries the full disclosure burden. It hints at an output-honesty constraint ('without inventing rank fields') but omits auth requirements, the scope/granularity of the daily aggregation, and any rate or data-freshness behavior for a mutation-free but underspecified tool.

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?

A single compact sentence with the core action front-loaded. It is tightly sized, though the trailing clause about rank fields is cryptic and consumes space that better parameter or usage guidance could have used.

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?

An output schema exists, so return values need not be explained, but with zero annotations, 0% schema description coverage, and no usage routing, the definition leaves an agent unable to distinguish this tool from its numerous Bing-stats siblings.

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% for two parameters. The word 'daily' loosely gestures at the 'days' parameter and 'Bing' gestures at 'site', but the description never explains the site value format or the window semantics, so it does not compensate for the coverage 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?

States a specific verb and resource: 'Return Bing daily clicks and impressions.' An agent can grasp the core purpose, though it never differentiates itself from close siblings such as bing_page_stats, bing_query_stats, or bing_url_traffic, so the boundary is left to inference.

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 when-to-use guidance, no prerequisites, and no named alternative among the many competing Bing stats tools. The only operative instruction is a negative warning ('without inventing rank fields'), which does not tell the agent when this tool is the right choice.

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