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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description usefully adds the sort behavior ('open ones first'), but says nothing about pagination, result volume, or the default 'all' state behavior beyond what the schema shows.

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 short sentences with zero filler; the resource identity and ordering behavior are front-loaded before the filter note.

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 read-only list tool with no output schema and only three optional params, this is close to sufficient. The one gap is the undocumented limit/pagination parameter, which the agent would need to know about to page results.

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 67%: state and provider are documented in the schema (including default and a reference to list_providers), while limit is undocumented anywhere. The description's 'Filter by state and provider' only restates the visible parameters, adding no format or constraint detail.

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 clear verb+resource ('Provider incidents') and adds scope detail (outages, degradations) that tells the agent what kind of incidents are returned. The verb distinguishes it from open_incident/update_incident siblings, but it does not explicitly say so.

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 mention of filtering by state and provider implies the retrieval use case, and the ordering note hints at why to prefer it over un-sorted alternatives. However, there are no explicit when-to-use/when-not statements or named alternatives (e.g. get_status vs list_incidents).

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