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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds genuine context beyond that: the event types returned, the fields available (start, end, message, open), and the newest-first ordering, which is real behavioral information.

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 dense sentence plus an endpoint reference. The return fields, ordering, limit behavior, and route are all front-loaded with no filler; every clause carries information.

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 usefully enumerates the event fields and ordering. It does not explain how the start/end range parameters filter the incident history or whether results paginate beyond the 5000 limit, which are minor gaps for a read-only lookup tool.

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 80%, and the schema leaves 'limit' entirely undocumented. The description compensates by explaining that limit=1 yields the most recent event, adding semantics the schema lacks, plus the newest-first ordering that governs how start/end and limit interact.

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: retrieves down/disabled events for a check, characterized as an incident history, and even names the underlying endpoint. It does not explicitly differentiate itself from the sibling nodeping_get_current_events, though 'history' and 'newest first' imply the distinction.

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 note 'limit=1 returns the most recent event' gives an implied usage pattern, and 'incident history' hints at the historical use case. However, there is no explicit when-to-use guidance or contrast with nodeping_get_current_events, nodeping_get_check_results, or nodeping_get_check_summary.

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