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

Annotations already declare readOnlyHint, idempotentHint, and closed-world, so the safety profile is covered. The description adds genuine behavioral value: results are sorted worst-first and each item carries impact, remediation, affected packages/products, and a page link. It could still note whether results can be empty or are bounded.

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?

One front-loaded sentence that names the resource, ordering, and returned fields with zero filler. The parenthetical examples add disambiguation without bloat.

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?

There is no output schema, but the description compensates by enumerating the fields each incident returns (impact, recommended action, affected packages/products, page). The only gap is the undocumented severity filtering behavior, otherwise an agent has what it needs to call and interpret this tool.

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 description coverage is 100% and the single severity parameter is fully documented with an enum, so the schema does the heavy lifting. The description never mentions the severity filter, adding 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?

States a specific verb (list) and resource (open incidents) and elaborates with concrete examples of what counts as an incident (critical flaws, big outages, supply-chain attacks). It does not explicitly distinguish itself from the sibling get_incident, though 'list' vs 'get' is reasonably inferable.

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?

Implicitly scoped to currently open incidents and ordered worst-first, which hints at usage. However, it never says when to pick this over get_incident (fetch one) or check_stack/check_repo, and gives no prerequisites or exclusions.

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