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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description contributes the weekly granularity and market-scoping behavior, but does not disclose the dependency on a Bing connection, any rate limits, or what a returned series looks like.

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?

One well-formed sentence, front-loading the verb and resource with no filler. Slightly thin for a four-required-parameter tool, but nothing is wasted.

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 4 required params, no schema descriptions, no output schema, and no annotation detail beyond the safety flags, the description should do more. It never explains the mandatory connectionId or what the response contains (a weekly impression series over what window?), leaving real gaps before an agent can call this confidently.

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% across 4 required parameters, so the description must carry the load. It usefully explains country/language with a concrete example ('us and en-US'), but leaves connectionId completely unexplained and does not describe keyword syntax or locale fallback behavior.

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 and resource: 'Read weekly Bing impressions for a keyword in a market' clearly states what data is returned and at what granularity. It does not distinguish itself from plausible siblings such as get_bing_report or get_tracked_keywords, which an agent could confuse with keyword-volume lookups.

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?

No guidance on when to use this versus get_bing_report, get_tracked_keywords, or list_bing_sites, and no prerequisites stated. The mention of 'market (country and language)' gives some context, but the caller must infer when Bing keyword volume is the right call.

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