get_query_page_stats

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

No annotations are provided, so the description carries the full burden. It mentions raising BingWebmasterError on failure but does not disclose authorization needs, rate limits, or what happens if the query returns no pages. Behavioral insights are minimal.

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 concise with distinct sections for args, returns, and raises. It is efficient and well-structured, though it sacrifices some detail for brevity.

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 that there is an output schema likely documenting return types, the description adequately addresses returns. However, it lacks usage context and behavioral details, making it incomplete for full agent decision-making.

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?

The description explains two of the three parameters (site_url and query) with brief, clear meanings. However, the 'self' parameter is left unexplained, and the schema has 0% description coverage, so the description partially compensates but not fully.

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 tool retrieves 'detailed traffic statistics for pages matching a specific query', with a specific verb and resource. This distinguishes it from siblings like get_page_stats (likely all pages) and get_query_stats (maybe overall stats).

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 description does not provide any guidance on when to use this tool versus alternatives. With a long list of sibling tools, explicit differentiation would be helpful, but none is given.

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