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

Annotations already establish readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: volumes reflect Bing searches only and should be read as relative demand and trends, and exact-match vs 'broad' matching is disclosed.

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 tight sentences, front-loaded with the core capability and the return shape, followed by a caveat about interpreting volumes. Every sentence contributes and nothing is padding.

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 no output schema, the description carries the burden of describing returns and does so well (weekly impressions, broad match, related keywords with volumes). It omits the relatedLimit cap and whether results are paginated, but is otherwise adequate for a 5-parameter read 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 coverage is 80%, so the schema already documents keyword, country, language and includeRelated, while the description only alludes to related-keyword output. It adds no syntax or format detail for relatedLimit or the country/language codes, so the baseline 3 is appropriate.

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 (search demand) plus resource (a keyword on Bing) and enumerates what comes back: weekly impressions over recent months, exact-match plus broad, and related keywords with volumes. The line 'Not tied to a site - any keyword works' implicitly separates it from the site-bound siblings like bing_top_queries and bing_search_performance.

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?

Gives clear context for when this tool applies ('any keyword works', not tied to a site) and how to read the output, which steers an agent away from site-scoped siblings. It stops short of naming an explicit alternative or excluding cases, so it falls below the 5 bar.

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