Bing Webmaster report

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context ('position summed over the range', daily granularity, that Bing's index feeds AI search products), but says nothing about auth requirements, rate limits, or date-range defaults.

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 dense, front-loaded enumeration with no filler; the metric details are attached inline to the report types they belong to. Every clause carries information.

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, and the description does compensate by describing what each report type returns and how metrics are aggregated over the range. The remaining gap is that date-range and `top` semantics are absent, which matters for a 5-parameter analytics tool.

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 only 20%, so the description must compensate. It partially does by mapping the report enum values to their meaning (queries/pages/traffic/crawl/crawl_issues), but the `top`, `startDate`, and `endDate` parameters get no mention at all.

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?

Specific verb+resource: it enumerates exactly what Bing data is returned (top queries/pages with clicks, impressions, CTR, position; daily traffic; crawl stats; crawl issues). The closing note that it 'complements Search Console' hints at the sibling boundary (search_analytics) but never names it explicitly, so an agent must infer the split.

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 implied by the enumerated report types and the Search Console complement note, but there is no explicit when-to-use/when-not guidance and no sibling tool is named (e.g. search_analytics, inspect_url, indexnow_submit). The agent must work out the routing itself.

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