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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered; the description adds genuinely new behavioral context, namely the 5-minute refresh cadence which tells the agent results may be slightly stale. It also enumerates what the response contains (per-service state and group, incidents with remediation).

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?

A single front-loaded sentence that covers purpose, payload, and refresh rate with no filler. The service list is illustrative rather than exhaustive, which keeps it compact, though the ellipsis makes the enumeration slightly loose.

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?

With no output schema, the description correctly carries the burden of explaining return values: summary sentence, per-service state and group, and incidents with recommended action. Only minor gaps remain, such as whether the service list is fixed or user-configured.

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 tool takes zero parameters, so there is nothing for the description to clarify; baseline 4 applies. The description does not falsely imply any inputs.

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?

States a specific resource and scope: the live status of the whole internet, aggregating watched services and open incidents. An agent can tell this is a broad summary rather than a single-incident lookup, but it never names the sibling tools (list_incidents, get_incident, check_stack) it differs from.

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?

Usage is only implied: the aggregate nature and 'one-sentence answer' suggest it's a first-stop check before drilling into a specific incident. There is no explicit when-to-use vs when-to-call-get_incident guidance and no stated exclusions.

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