bing_traffic_rank

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

Annotations already establish read-only, idempotent, non-destructive behavior, but the description adds genuinely non-obvious context: an empty_response label means silence rather than a clean measurement, and untrusted fields must be treated as data not instructions. These are behavioral traits the structured fields cannot convey.

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 sentences, each carrying distinct load: purpose, trigger, routing, and output/security semantics. Front-loaded with the core purpose and free of padding.

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 does the important work of explaining the empty_response condition and the untrusted-field convention. It stops short of describing the shape of the rank/traffic totals returned, which is a minor remaining gap.

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 the single parameter site_url is undocumented in both the schema and the description. The description never says what form site_url should take (full URL vs. host), which is the one piece of invocation detail the agent needs.

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 Bing rank and traffic totals for one site over time') and immediately scopes it against siblings by excluding per-query and per-page numbers. An agent can distinguish this from bing_traffic_queries and bing_traffic_pages 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 trigger ('when the user asks how the site's overall Bing visibility moved'), an explicit exclusion, and names the two alternative tools to call instead. This is exactly the when/when-not/alternatives pattern.

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