bing_traffic_pages

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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is not obligated to restate it. It adds genuinely new behavior: the empty_response label meaning 'silence, not a measurement' and the instruction to treat untrusted fields strictly as data. That is useful edge-case and prompt-injection guidance beyond structured fields, though return shape/pagination is still unstated.

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-loaded purpose followed by usage, an exclusion with a named alternative, an empty-result edge case, and a security directive. Every sentence earns its place with no 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?

No output schema exists, and the description compensates by explaining the empty_response label. For a single-parameter read tool with rich annotations this is nearly sufficient; the missing piece is the site_url input format, which is not fully covered by any source.

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?

One parameter (site_url) at 0% schema description coverage, so the description carries the full burden — yet it never states the expected URL format (scheme, host-only vs. path, whether a domain property or full URL is required). The phrase 'one site' loosely implies the scope but gives no syntax guidance.

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 pages on one site that received Bing search traffic') and immediately distinguishes itself from the sibling bing_traffic_page, which covers the queries behind a single page. An agent can route 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?

Explicit when-to-use ('which pages earn Bing traffic or which URLs lost clicks') plus an explicit when-not with a named alternative ('Do not use this for the queries behind one page; call bing_traffic_page'). 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.