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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds real value beyond that: UTC semantics of the timestamps, the 7-day hard cap, the definition of an outage, and the two data sources merged into the result.

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?

Two dense sentences plus a use-case clause, with the core definition front-loaded and the routing guidance last. No filler and nothing repeated from the schema or annotations.

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?

For a two-parameter, read-only, no-output-schema tool this is close to complete: it explains what an incident is, the time window, the filter, and the intended judgment call. The only real gap is behavior at the 7-day boundary and the shape of the returned records.

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 0%, so the description must carry both parameters, and it largely does: 'last N days (max 7)' bounds the days parameter and 'optional provider name filter' explains name. It omits the default of 7 and does not say what happens if days exceeds 7 (clamp vs error).

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 names the resource (outages and vendor status-page incidents) and even defines the term 'outages' as consecutive failed probes, which is more than the title supplies. It is clearly distinct from list_tools/recommend/tool_status, though it never explicitly contrasts itself with them.

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?

It gives an explicit decision context: 'Use to judge whether a failing API is a known incident.' That tells the agent when this tool is the right call. It stops short of naming alternatives or when-not-to-use conditions, so it falls just below the top band.

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