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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the bar is lower, but the description still adds real value by naming exactly what is destroyed: the check's results and incidents. It does not state whether the deletion is permanent/irreversible or how a repeated call behaves, which idempotentHint=false implies matters.

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 short sentences, front-loaded with the action and immediately followed by the destructive side effect. Zero filler; every clause carries information.

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 no-output-schema destructive tool whose annotations cover the safety profile, the description supplies the key missing piece (what data is lost). It stops short of covering irreversibility or repeat-call behavior, but nothing essential to invoking it correctly is 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%, and the parameter descriptions already explain where check_id and instance_id come from plus the passport_token fallback. The description adds nothing about parameters, so the baseline of 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?

States a specific action and resource: stopping the watch on a URL, with the added consequence that its results and incidents are deleted. It is clearly the inverse of uptime_add and distinct from uptime_status, though it never names those siblings explicitly.

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 action is self-evidently used when you want to stop monitoring a URL, so usage is implied rather than stated. There is no explicit when-to-use/when-not guidance, no mention of prerequisites (e.g., the check must exist), and no routing to uptime_add/uptime_status for alternatives.

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