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

readOnlyHint=true already tells the agent this is a safe read. The description goes beyond annotations by disclosing what the payload contains (update timeline, affected components), which matters since no output schema exists. It stops short of noting auth requirements, error behavior for unknown ids, or rate limits.

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?

The sentence is front-loaded with the core action and payload scope, with no filler. The trailing 'Instatus: GET /v1/{page_id}/incidents/{incident_id}' is mildly redundant with the tool name but useful for mapping to the REST endpoint.

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 single-resource getter with full parameter documentation and annotations covering the safety profile, the description supplies the missing piece (what the response contains). Only minor gaps remain around auth and error cases, which are low-value here.

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 required params (page_id, incident_id) documented in the schema itself. The description only refers generically to 'id' and adds no format, naming, or lookup guidance beyond what the schema provides, 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 ('Get a single incident by id') and further scopes it with the returned content ('full state including its update timeline and affected components'). This clearly separates it from the sibling list_incidents and the create/update/delete incident tools.

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 implied: call it when you have a page_id and incident_id and need one incident's full detail rather than a list. However, it never explicitly says when to prefer this over instatus_list_incidents or instatus_get_maintenance, nor states any prerequisites.

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