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

Annotations already declare the full safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the description only needs to add context. It does so by describing what comes back – status, impact, and affected components – which is valuable since no output schema exists. It omits pagination, result-count limits, and how far back "recent" reaches.

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 sentences, no filler, with the purpose front-loaded and the return-value detail second. Every clause carries information the agent needs, especially given the absent output schema.

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 simple read-only listing tool with one optional param, rich annotations, and no output schema, this covers purpose and expected return content adequately. It falls short of complete only in not clarifying pagination/recency bounds or the distinction from get_statuspage_incident.

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?

There is a single optional parameter whose schema coverage is 100%, so the schema already explains the query filter fully. The description never mentions the query parameter or how filtering interacts with the incident summary, so it adds no meaning beyond the schema – baseline 3 applies.

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 gives a specific verb and resource ("List incidents from the RudderStack status page") and scopes it to recent incidents. It implicitly distinguishes itself from the singular sibling get_statuspage_incident, but never names that alternative explicitly.

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 by the phrase "recent incidents" – the agent can infer this is the browse-everything tool versus a single-incident lookup, but there is no explicit when-to-use, when-not-to-use, or named alternative. No prerequisites or caveats are stated.

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