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

Annotations already include destructiveHint=true, but the description adds the explicit warning that deletion is permanent and irreversible. This goes beyond the structured annotation and clarifies the consequence of calling the tool, which is valuable for an AI agent considering this action.

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 extremely concise—two short sentences—and front-loads the core action before adding the irreversibility warning. Every word earns its place; no filler or redundancy.

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 one parameter and no output schema, the description is fairly complete. It states the action and the key consequence (permanent). While it doesn't describe the id format or any failure behavior, the simplicity of the tool and presence of annotations reduce the need for more.

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 provides no additional meaning for the only parameter 'id'. Schema coverage is 0%, so the description carries the full burden, but it simply restates the tool's intent without explaining any parameter to the agent. The schema only defines 'id' as a required string, and the description does not compensate.

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 a specific verb ('delete') and resource ('monitor'), and adds 'Permanently' to emphasize irreversibility. It clearly distinguishes this tool from sibling monitor tools like monitors_create and monitors_update by indicating a delete 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?

There is no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, dependencies, or when a monitor cannot be deleted. The only usage hint is implicit from the name and the warning 'Cannot be undone.'

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