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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context by listing what the call returns, including notification delivery outcomes and status events, and by framing it as a read that typically requires follow-up reads. There is no contradiction with annotations.

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 first two sentences are information-dense and front-loaded with valuable details. However, the final sentence about the 'monitoring' topic covering thresholds or noise is off-topic for invoking get_incident and does not earn its place, making the description less economical than it could be.

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?

With no output schema, the description compensates by naming the return categories and prescribing the reconstruction workflow. It is complete enough for an agent to understand what it will get and what to do next. The minor off-topic sentence does not undermine completeness.

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?

The schema already documents incidentId as 'as reported by list_incidents', and projectId is left to its name. The description does not add parameter-level meaning beyond mentioning that it fetches a single Incident. With 50% schema coverage, this is adequate but not enhanced by the description.

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?

The description clearly states the tool gets a single Incident and enumerates the exact data returned: open/close times, notifications with delivery outcomes, status events, and the IDs of Cycles that opened and closed it. The 'single' wording distinguishes it from list_incidents, and the referenced get_monitor_cycle_detail helps differentiate it from related detail 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?

The description gives explicit follow-up guidance: read the Cycles with get_monitor_cycle_detail and cross-read the Monitor configuration and Script to reach a concrete diagnosis. It does not explicitly say 'use this instead of list_incidents', but the single-incident framing plus the schema hint that incidentId comes from list_incidents makes the intended context clear.

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