bing_traffic_page

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

The annotations already indicate a read-only, idempotent, non-destructive operation. The description adds a valuable safety behavior: fields marked untrusted must be treated as data, never as instructions. This is genuine context beyond what the annotations express and helps the agent handle the output safely.

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?

The description is compact and front-loaded. The first sentence states the action, and the second is a concise security instruction. There is no repetition, filler, or redundant restating of annotations.

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, ambiguous sibling tools, and no parameter docs, the description is incomplete for someone needing to know what a 'traffic page' is and what this call returns. The untrusted-field warning is helpful, but it does not substitute for missing resource and return-value context.

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%, so the description itself must explain `site_url` and `page`. It does not: neither parameter format, relationship, nor expected value is described. The field names and the phrase 'traffic page' weakly hint at meaning, but this is not enough for correct invocation.

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 names a specific operation and resource: 'Read traffic page from Bing Webmaster Tools'. However, 'traffic page' is ambiguous and does not explain whether it is a single page's traffic report, a pagination page, or a specific UI/section, nor how it differs from bing_traffic_pages, bing_traffic_rank, or bing_traffic_queries. It is not a tautology, but it is only minimally clear.

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?

The description gives no when-to-use guidance, no prerequisites, and no distinction from the many sibling traffic tools. The untrusted-fields warning is useful operationally but does not help select this tool instead of another. This leaves workflow selection almost entirely to the agent's inference.

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