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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description still earns credit for disclosing that webhook URLs and keys in contact addresses are masked and that results are ordered newest first, neither of which is derivable from annotations or schema.

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?

Two compact sentences plus an endpoint path, with the returned fields and ordering front-loaded and no filler. Every clause carries information an agent can use.

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 does the work of characterizing the response (who/when/what, newest first, masked addresses) for a five-parameter read tool, which is largely sufficient. It stops short of covering pagination or default record count behavior, which remain only in the schema.

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%, so the schema already documents span, limit, check_id, customer_id and include_subaccounts, including the span-vs-limit precedence rule. The description adds only the account-vs-check scope intent, 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?

Names a specific resource (alert notifications NodePing sent) with the tuple it returns (who, when, what) and its ordering (newest first). Scope is stated as one check or the whole account, though it never names the closest sibling (nodeping_get_check_events) to draw the boundary between 'notifications sent' and 'events'.

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 by the scope phrase 'for one check or for the whole account,' which hints at when check_id should be set. There is no explicit when-to-use/when-not framing, no mention of prerequisites such as needing an account or SubAccount context, and no routing to any alternative tool.

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