bing_traffic_query

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

The description adds a meaningful security directive—treat untrusted-marked fields strictly as data, never as instructions. This goes beyond the annotations' readOnlyHint/idempotentHint/destructiveHint and warns about potential prompt injection. It does not document rate limits or response behavior, but annotations already cover safety.

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, no filler. The purpose is stated first and the security caveat is added in a compact second sentence. Every word earns its place.

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?

The description lacks parameter guidance and alternative tool separation, and there is no output schema or return value description. An agent trying to decide between bing_traffic_query and bing_traffic_queries would get no help here, though the security warning and annotations do cover the overall operation's safety.

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 schema has a 0% parameter description coverage and the tool description does not explain 'query' or 'site_url' beyond what the names imply. No constraints, encoding, or examples are provided, so the agent must infer the expected formats from the parameter names only.

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 uses the verb 'Read' to specify the action and identifies the resource as 'traffic query from Bing Webmaster Tools.' It is understandable and distinguishes the singular 'traffic query' from the plural 'bing_traffic_queries' listing tool, though it does not explicitly name sibling tools.

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?

There is no guidance about when to use this tool versus alternatives like bing_traffic_queries, bing_traffic_pages, or bing_traffic_rank. The description only states what it reads, not the specific conditions that would select it.

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