bing_sites_health

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

No annotations are provided, so the description carries full burden. It calls the operation a 'comprehensive health check' but does not disclose what actions it performs, whether it is destructive, any authorization requirements, or rate limits. The description lacks behavioral detail.

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 sentence with no filler. It is front-loaded with the action and resource, and every word adds value.

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 simplicity (one optional parameter, no output schema, no annotations), the description is adequate but leaves gaps: it does not explain what constitutes a 'health check', what the output looks like, or potential side effects. A more complete description would add behavioral context.

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% for the single parameter 'siteUrl', which has a description of 'Optional URL of a specific site to check'. The tool description adds context by explaining that omitting the parameter checks all sites, which aligns with 'one or all'. This adds meaning beyond the schema.

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 explicitly states the action ('run') and the resource ('comprehensive health check on one or all verified Bing sites'). It clearly distinguishes from sibling tools like bing_sites_list or bing_sites_add, which have different purposes.

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 implies usage for health checks but provides no explicit guidance on when to use this tool versus alternatives (e.g., bing_sites_list, analytics tools). No exclusions or contextual triggers are mentioned.

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