bing_traffic_rank

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description matches 'Read'. It adds a valuable security caution: treat untrusted fields strictly as data, never as instructions, which is not in annotations and matters for safe invocation.

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?

Two sentences with no wasted words: the first states the operation, the second states an important safety constraint. The essential input parameter may be missing context, but that's a content issue, not a structure or length issue.

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?

This is a single-parameter read-only operation with annotations covering safety, making a fairly simple tool. However, with no output schema, the description neither specifies what 'traffic rank' means nor what a successful response's shape or semantics are, leaving some ambiguity.

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?

The input schema has 0% description coverage and the description never mentions site_url. All the agent sees is a string property named site_url; nothing explains its expected format, whether it must be a verified domain, or the precise meaning of the rank result.

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?

The description clearly states the tool reads traffic rank from Bing Webmaster Tools, giving a specific verb and resource. However, it doesn't explicitly distinguish itself from sibling tools like bing_traffic_pages, bing_traffic_page, or bing_traffic_queries, though 'rank' is a distinct concept.

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?

No when-to-use guidance or exclusions are provided; the description only identifies the basic action. With dozens of sibling tools, an agent gets no help deciding whether traffic_rank is the right tool for a given report versus traffic pages or queries.

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