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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add what annotations don't say. It does add the payload structure — timeline, per-hour reasons, claims — but that overlaps with the output schema and it says nothing about behavior on a nonexistent id or whether the response is capped.

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?

A single front-loaded sentence with no filler. The parenthetical-style breakdown of return contents is compact and informative rather than verbose.

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 one-parameter read tool with a full output schema, the description covers purpose, provenance of the id, and the shape of the result. The main gap is error behavior for an unknown id, which an agent might reasonably want to know before calling.

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 0%, so the single incident_id parameter is undocumented in structured fields. The description compensates partially by saying the id comes 'from list_incidents', which tells the agent where to source a valid value, but it adds no format or validation detail beyond the schema's integer type.

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?

Names a specific verb and resource ('One incident by its id') and explicitly distinguishes itself from the sibling list_incidents as the single-item drill-down. It also previews what comes back (timeline, hourly reasons, claims), so the agent knows exactly what this tool yields versus the list tool.

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?

The phrase 'from list_incidents' establishes the intended workflow: call the lister first, then fetch a specific incident by id. It doesn't state when not to use it or what happens with an invalid id, but for a simple read-by-id tool the usage context is clear.

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