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

The annotations already declare destructiveHint=true, and the description reinforces this by saying 'Permanently delete' and 'Cannot be undone.' It adds useful context beyond the annotation by clarifying the deletion is irreversible, which is meaningful behavioral information for the agent to relay to the user.

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 description is only nine words across two sentences, with the key action front-loaded. Every word contributes: 'Permanently' and 'Cannot be undone' convey the destructive and irreversible nature; no filler or redundant phrasing exists.

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 simple delete operation with destructiveHint annotation, the description is largely sufficient: it names the target resource and the irreversible consequence. There is no output schema, but a delete tool typically does not require detailed return-value documentation. Minor gaps include not stating what happens to associated checks or events, but this is unlikely to prevent correct invocation.

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 description adds no parameter-level detail on its own, but the input schema covers 3 of 4 parameters with clear descriptions. The 'id' parameter lacks a description, and the tool description does not clarify that id refers to the monitor identifier, though that is strongly implied by the tool name and delete semantics.

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 states an exact verb and resource: 'Permanently delete a monitor.' This clearly distinguishes the operation from sibling tools like monitors_create, monitors_update, and monitors_trigger. The additional warning 'Cannot be undone' removes any ambiguity about the nature of the action.

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 implies the tool should be used when the user wants to remove a monitor permanently, and the 'cannot be undone' warning functions as a caution against casual use. However, it does not explicitly say when to use it versus alternatives or mention any prerequisites or exclusions, so the guidance is implied rather than stated.

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