Traffic trend

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the metrics returned (clicks and impressions), which annotations do not convey, but says nothing about date-range defaults for the optional dates or the time granularity of the series.

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 sentence with no filler, front-loading the resource and scope. Nothing is wasted or buried.

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?

There is no output schema, so the description should carry more of the return-shape burden. It names the metrics but not the interval/granularity of the series or what happens when startDate/endDate are omitted, which are the details an agent most needs for a trend call.

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 100%: siteUrl's format, the list_sites fallback, and the YYYY-MM-DD pattern for startDate/endDate are all documented in the schema. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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 (time series of clicks and impressions) and scope (whole site, in Bing), so an agent knows it returns trend data rather than a snapshot. The phrase 'whole site' implicitly distinguishes it from get_query_trend and get_url_traffic_info, but those siblings are never named.

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?

Usage is only implied: 'whole site' suggests this is the aggregate trend view as opposed to the query- or page-level trend siblings, but there is no explicit when-to-use statement, no prerequisites, and no named alternative. Adequate but leaves routing to inference.

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