traffic_trend

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

No annotations are provided, so the description carries the full behavioral burden. It reveals the data source (Bing) and the daily granularity, which is useful, but says nothing about authorization requirements, whether the site must be verified, or any limits on lookback period. For a read-only analytics call the risk profile is low, but the usage context is undocumented.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity contributes to the gaps in guidance and parameter documentation rather than being a strength.

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?

An output schema exists, so return format need not be explained, but the tool lives in a webmaster toolbox full of adjacent analytics and indexing tools with no annotations, no parameter text, and no usage context. The description is not complete enough to disambiguate the tool from its siblings.

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 two parameters are undocumented in structured fields. The description hints only loosely at site_url via 'for the site' and never mentions the 'days' parameter or its 90-day default, leaving the caller to infer the time window from the schema alone.

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 resource and metric combination (daily Bing clicks and impressions), which is more informative than a bare name restatement. However, it does not distinguish itself from overlapping siblings like search_performance or traffic-oriented tools, so an agent cannot tell from the text alone which of the adjacent analytics tools to pick.

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 when-to-use guidance, no mention of prerequisites (e.g. a connected Bing Webmaster Tools property), and no reference to alternative tools. The sibling set contains search_performance and list_sites, which could plausibly overlap, and the description gives no routing help between them.

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