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

With readOnlyHint=true already covering the safety profile, the description still adds real behavioral context: deterministic ordering ('most recent first') and the shape of each returned incident (id, name, status, impact, components, updates, timestamps). It does not mention pagination behavior beyond what the schema's page/per_page params imply.

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?

Front-loaded with the core action and result shape in essentially one dense sentence, with the API mapping trailing as a useful reference. Every clause carries information, though the field enumeration borders on schema duplication.

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 paginated list tool, the description plus fully-documented schema and readOnlyHint annotation cover what an agent needs to invoke it correctly. Only minor gaps remain, such as explicit pagination/ordering interaction or total-count behavior.

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%, so the schema already documents page, per_page, status, and page_id with defaults and bounds. The description only echoes the status filter and adds no format or syntax detail beyond the schema, so the 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 and resource (list a status page's incidents) plus ordering ('most recent first') and the optional status filter, and even maps to the underlying endpoint. It is clearly distinguishable from instatus_get_incident, but it never names a sibling explicitly the way a top-tier definition would.

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?

'Optionally filtered by status' implies the filtering use case, but there is no explicit guidance on when to use this list versus instatus_get_incident or instatus_list_maintenances, nor any prerequisite or exclusion statements. Usage is implied rather than specified.

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