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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that by disclosing the payload contents (messages and affected components) and the underlying endpoint GET /incident/list/active/{statuspage_id}, which helps an agent reason about external data. It does not mention pagination or rate limits, so it is not a 5.

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 compact sentences that are front-loaded with the scope qualifier and then the endpoint; every clause carries information and there is no filler.

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, the description usefully names the returned content (messages, affected components) and the pagination caveat lives in the schema. Nothing critical is missing, though it could note that an empty page ends iteration.

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% – both page and statuspage_id carry full descriptions including the no-totals/paginate-until-empty behavior – so the schema does the heavy lifting. The description adds nothing about parameters beyond restating the id in the URL path, which is the baseline 3 case.

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 (active incidents) and scopes it as 'Active (unresolved)', which implicitly separates it from statusio_list_incidents and statusio_list_resolved_incidents. It does not name those siblings explicitly, so the differentiation requires the agent to infer it from the scope word.

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: 'Active (unresolved)' tells the agent this is the right tool when it wants open incidents, but there is no explicit when-to-use statement, no mention of the resolved/complete alternatives, and no prerequisites such as required page_id.

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