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

readOnlyHint=true already covers the safety profile, and the description adds useful context beyond it: the exact set of fields returned and the underlying endpoint (GET /api/v3/incidents/{id}). It does not address behavior on an unknown id or error/pagination semantics, so it stops short of full disclosure.

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?

One front-loaded sentence carrying the return-field detail, followed by a short endpoint reference. No filler and no repetition of the title.

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 single-parameter read tool with no output schema, the description compensates by naming the returned fields, which is exactly what an agent needs to decide whether this call answers its question. Only the missing not-found/error behavior keeps it from a 5.

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% and the schema itself documents where incident_id comes from (betterstack_list_incidents). The description only restates 'by id' and adds no format, validation, or lookup guidance 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+resource ('Get a single incident by id') and enumerates what the response contains (cause, status, timeline timestamps, acknowledger/resolver, related monitor). 'Single incident by id' cleanly separates it from the sibling list_incidents without needing to name it.

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: an agent can infer this is the detail-fetch that follows list_incidents, and the schema's parameter description reinforces that by pointing at betterstack_list_incidents as the id source. However, there is no explicit when-to-use/when-not guidance and no mention of alternatives such as get_monitor for the related monitor.

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