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

Annotations cover the safety profile (readOnly, non-destructive, open-world), and the description adds substantial context on top: aggregation across a window, CTR expressed as a 0-100 percentage, impression-weighted average position, the rowCount/totalRows distinction, and the notConfigured: true condition when no API key exists.

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?

Front-loads the purpose, then metric details, then rowCount/totalRows semantics, then the notConfigured edge case. Every sentence carries information, though the three-sentence structure is slightly dense rather than maximally scannable.

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?

For a windowed-stats read tool with a rich output schema and full annotation coverage, the description supplies everything an agent needs: scope, metric definitions, truncation semantics, and the no-API-key state. No material gap remains.

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 75% and the schema itself documents limit, startDate, and endDate thoroughly (format, defaults, 'never pass null'). The description adds only the limit-related rowCount semantics and the unset-API-key behavior, so it largely leaves parameter meaning to the schema — baseline 3.

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?

Names a specific verb+resource ('top search queries on Bing Webmaster Tools for a property') and enumerates the metrics returned. It also explicitly positions itself as 'the Bing counterpart to query_top_queries', letting an agent distinguish it from the many sibling get_* stats tools without opening a schema.

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?

The reference to query_top_queries gives a clear routing cue for when to pick this tool over the Google-side equivalent. It does not, however, state exclusions or contrast it with get_bing_keyword_stats / get_bing_query_page_stats, so it stops short of explicit when-not guidance.

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