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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds the irreversibility context ('cannot be undone') and specifies what gets destroyed (a LastPing monitor by UUID), giving useful behavioral warning beyond the structured flags.

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 sentences with no filler: the first delivers action, target, and parameter; the second delivers the critical warning. The most important qualifier ('permanently', 'cannot be undone') is front-loaded.

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-required-parameter destructive tool with annotations covering the safety profile, the description provides all essential context: what is deleted, how it is identified, and that the action is irreversible. No output schema or complex behavior requires additional explanation.

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 id parameter already has 'Monitor UUID' as its description. The tool description only repeats 'by UUID' without adding new semantic details, so it meets but does not exceed the baseline.

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 names a specific action ('permanently delete'), a specific resource ('a LastPing monitor'), and the key identifier ('by UUID'). It clearly differentiates this from sibling tools like pause_monitor or snooze_monitor, which temporarily alter monitor state.

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?

'Permanently delete' and 'This cannot be undone' convey the intended use case: full removal when recovery is not desired. It does not explicitly name alternatives such as pause_monitor for temporary disablement, so it stops short of full when/not-when guidance.

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