bing_traffic_queries

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

Annotations already declare the read-only/idempotent/non-destructive profile, and the description adds behavior the annotations cannot: that an empty result carries an empty_response label meaning 'silence, not a measurement', plus a directive to treat untrusted fields as data only. This is exactly the added-context value the annotations do not supply.

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?

Front-loads purpose before routing and caveats, and every sentence carries distinct information (scope, trigger, exclusion, empty-result semantics, injection safety). It runs slightly long, but no sentence is filler.

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, the description covers the most important return-shape caveat (empty_response) that an agent would otherwise misreport. The remaining gap is the site_url input contract, which is neither in the schema nor the description.

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 the single site_url parameter, so the schema adds nothing. The description only indirectly implies the parameter identifies the site to scope results to; it gives no format, host-vs-property, or required-ness guidance, so it only partially compensates for the 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 ('List the search queries that brought Bing traffic to one site'), which distinguishes it immediately from the sibling bing_traffic_query that tracks one query over time. An agent can pick correctly without opening either schema.

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?

Gives an explicit positive trigger ('when the user asks which queries a site shows for, or why clicks changed') and an explicit negative one with the alternative named ('Do not use this for one query's trend over time; call bing_traffic_query'). Nothing is left to inference.

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