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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond that: it is not tied to any property (no siteUrl), and it returns notConfigured: true when no API key is configured, which surfaces an auth-state behavior an agent would otherwise miss.

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?

Three sentences, front-loaded with the core purpose, then the property-independence, then the auth edge case. Efficient and no filler, though slightly dense.

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 an output schema present, return values need not be explained, and the description still covers the notable notConfigured case. Complete enough for a single-keyword read tool; a note on how it differs from sibling Bing query tools would close the remaining gap.

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%, so country/language/keyword are already documented in the schema. The description adds only the negative detail that no siteUrl is needed, which is helpful but not parameter-level semantics beyond the schema baseline.

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 verb+resource (historical impression volume for a single keyword) with scope qualifiers (weekly buckets, broad-match impressions) and explicitly anchors it to Bing Webmaster Tools marketplace data. Clear enough to distinguish from the sibling get_bing_query_stats/get_bing_query_page_stats calls.

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?

Says it is 'useful for gauging Bing search demand and seasonality,' which implies the use case, but never states when to prefer it over the many sibling Bing tools (e.g., get_bing_query_stats) or any exclusion conditions. Context is implied rather than spelled out.

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