bing_analytics_page_query

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

The description only states the generic purpose. With no annotations, it fails to disclose behavioral traits such as whether the operation is read-only, any authentication requirements, rate limits, or what 'query performance stats' entails (e.g., metrics included). This leaves the agent without crucial behavioral context.

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, efficient sentence that conveys the core purpose without extraneous words. It is well-structured for quick understanding.

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 the lack of output schema and annotations, and the presence of many sibling tools, the description is too minimal. It does not explain what 'query performance stats' are, how the date parameters affect the results, or how this tool differs from similar ones like bing_analytics_query_page (which might be identical). The agent lacks essential context to use it effectively.

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 input schema has 100% description coverage, so the baseline is 3. The description adds no additional meaning to the parameters; it simply restates the tool's purpose. For example, it does not explain the relationship between siteUrl and pageUrl or the date range format beyond what schema already provides.

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 specific action ('Get query performance stats') and the target resource ('for a specific page from Bing Webmaster Tools'). It distinguishes from siblings like bing_analytics_page and bing_analytics_query by combining both page and query dimensions.

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 is provided on when to use this tool versus alternatives (e.g., bing_analytics_page for general page stats, bing_analytics_query for general query stats). There is no mention of prerequisites, context, or exclusions.

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