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

readOnlyHint=true already tells the agent this is a safe read, so the description carries a lighter burden. It adds the underlying REST route (GET /status_pages/{subdomain}/incidents/{incident_id}), which is mildly useful context, but says nothing about 404 handling or the shape of the returned incident.

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 the core action front-loaded and no filler. The endpoint restatement is slightly redundant but not wasteful enough to penalize heavily.

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 simple single-resource read with fully documented parameters and annotations covering the safety profile, the description is essentially sufficient. No output schema exists, so no return-value explanation is owed, though a note on not-found behavior would round it out.

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 100%, with both subdomain and incident_id described in the schema, so the baseline is 3. The description adds no syntax, format, or override semantics beyond what the schema already documents.

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 ('Get a single incident by its id'), making it distinguishable from the list-style sibling statuspal_list_incidents. It stops short of explicitly naming the sibling it contrasts with, so it is clear but not fully differentiated.

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: the id-based lookup signals 'fetch details for one known incident.' There is no statement of when to prefer this over statuspal_list_incidents or statuspal_get_status, and no mention of preconditions or error behavior for a missing id.

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