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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds valuable context by specifying exactly what is destroyed: the prompt, domains, and results. It does not explicitly state irreversibility, but the destructive annotation and 'deletes' wording make the consequence clear.

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 two short sentences and front-loads the destructive action. The second sentence is somewhat redundant with the required schema field, but it does not bloat the definition.

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 one-parameter destructive tool with rich annotations and full schema coverage, the description is nearly complete. It covers the action, the deletion scope, and the required identifier; only minor details like behavior when the monitor does not exist are absent.

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 single monitor_id parameter is fully documented in the schema. The description only repeats that monitor_id is needed, adding no syntax or format details beyond the schema.

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 and resource: it stops an existing monitor and deletes its prompt, domains, and results. This is clear and distinct from the sibling status/check tools, but it does not explicitly name or differentiate against those siblings.

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 is used to cancel a monitor, but it gives no explicit when-to-use guidance, no when-not-to-use conditions, and no mention of alternatives such as monitor_status.

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