bing_url_traffic_info

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it explains the empty_response label semantics ('silence, not a measurement') and warns against reporting it as 'no problems found', plus a prompt-injection guard on untrusted fields. These are non-obvious behavioral traits an agent could not infer from structured data.

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?

Four short sentences, each carrying a distinct load: scope, positive trigger, exclusion + alternative, and result-semantics caveats. The routing constraint is front-loaded and nothing is redundant.

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 usefully covers return semantics (empty_response) and safety caveats, and annotations cover the read-only profile. The one real gap is parameter meaning, which is unaddressed given 0% schema coverage; otherwise an agent has what it needs to call this correctly.

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% and both required parameters (site_url, url) are undocumented in the schema. The description only alludes to 'one URL' and never clarifies the distinction between site_url and url, their formats, or whether site_url is a property/account scope. With 0% coverage the description was expected to compensate and does not.

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 ('Read the Bing search-traffic record for one URL') and explicitly distinguishes itself from the sibling bing_url_info by naming the out-of-scope cases (crawl status, HTTP status). An agent can tell this apart from bing_traffic_page / bing_children_url_traffic_info without opening any 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 how much traffic one URL gets from Bing'), an explicit negative trigger ('do not use this for crawl status or HTTP status'), and names the alternative to call instead ('call bing_url_info'). This is the full when/when-not/alternative triad.

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