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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds the valuable detail that this returns the complete incident record including messages, which is the main behavioral distinction from the message-level sibling; it does not mention rate limits or error behavior, but those are minor here.

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 with zero filler, front-loading what the tool returns and following with the underlying endpoint. Every clause earns its place.

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, so the description carries the return-value burden, and it does so by naming the main payload sections. For a single-resource read with full schema coverage and clear annotations, nothing critical is missing, though a note on missing/deleted incidents would be a bonus.

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%, with both incident_id and statuspage_id fully documented (including the connection-default behavior for statuspage_id), so the baseline is 3. The description adds no parameter-level detail beyond the schema, which is acceptable given the schema does the work.

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 and resource ('One incident in full') and enumerates the payload scope: components, containers, infrastructure affected, and all messages. The 'all its messages' phrasing implicitly separates it from statusio_get_incident_message and the list tools, though it never names them outright.

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 tool name and the incident_id parameter description ('from statusio_list_incidents or the active/resolved lists'), which is enough to infer the list-then-fetch flow. There is no explicit statement of when to prefer this over get_incident_message or the list variants.

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