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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior. The description adds valuable context by enumerating exactly what the tool returns (status indicator, status line, degraded components, open incidents, maintenance) and notes that maintenance is shown 'where the page publishes it', implying variability. No contradiction with annotations.

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 long but information-dense, front-loaded with a question and followed by a structured list of outputs and use cases. The lengthy vendor enumeration is somewhat redundant given a sibling tool (statuspage_list_vendors) exists, but it serves as useful examples. Overall, every sentence contributes to understanding the tool's purpose and behavior.

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 absence of an output schema, the description effectively communicates the return contents (status, components, incidents, maintenance) and usage. It also clarifies the status_host parameter for arbitrary vendors. It doesn't describe the exact response format or potential limitations (e.g., rate limits), but for a simple status-check tool with strong annotations, it is sufficiently complete.

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?

Input schema coverage is 100% with detailed descriptions for all three parameters. The description reinforces the status_host usage ('Pass status_host to check any other vendor running a Statuspage') but this largely mirrors the schema's explanation. Since the schema already carries the semantic load, the description adds minimal extra meaning beyond what's provided.

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 opens with a clear question ('Is a service down right now?') and specifies the tool's function: checking live service status for 190 Statuspage vendors. It lists concrete return elements (status indicator, status line, degraded components, incidents, maintenance) and adds a status_host option for any other vendor, making the scope unmistakable.

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 explicitly states when to use it ('Use for questions about downtime, outages, service health, incidents in progress and whether an API or platform is working'). However, it does not mention alternatives such as statuspage_incidents for incident-only queries or statuspage_multi_check for multiple vendors, so it lacks exclusions and alternative guidance.

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