bing_analytics_query

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

With no annotations, the description must disclose behavioral traits. It only states it gets stats, but doesn't confirm it's read-only, doesn't mention authentication, rate limits, pagination, or the nature of the response. The agent lacks critical behavioral context beyond the action.

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?

The description is a single concise sentence that conveys the core purpose. It is front-loaded and efficient, though it lacks structure (e.g., no bullet points or separate sections). The null title means the description bears all the weight.

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?

Given 5 parameters, no output schema, and many sibling tools, the description is incomplete. It doesn't explain what 'query performance stats' includes, how results are formatted, or how to interpret the output. It fails to disambiguate from similar tools in the sibling list.

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 100%, so baseline is 3. The description adds no new meaning to the parameters beyond what the schema already provides. The parenthetical '(Top Queries)' is vague and does not clarify which parameter affects that concept.

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?

The description clearly states the action ('Get') and resource ('query performance stats') from a specific source (Bing Webmaster Tools). However, it does not differentiate it from siblings like 'bing_get_top_queries' which also deals with top queries. The parenthetical '(Top Queries)' provides some context but could be confused with other tools.

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 usage guidelines are provided. The description does not specify when to use this tool over alternatives such as 'bing_analytics_compare_periods' or 'bing_get_top_queries'. There is no mention of prerequisites, context, or when not to use it.

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