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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds the cascade scope (checks, results, stored page versions are destroyed) and irreversibility, plus a mandatory user-confirmation workflow. It does not cover failure behavior (e.g. deleting a currently running monitor) or errors, so it is strong but not exhaustive.

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 compact sentences, front-loaded with the destructive scope and irreversibility, followed by the confirmation requirement and the alternative tool. No filler.

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-parameter destructive tool with an output schema present, the description supplies what annotations and schema cannot: cascade scope, irreversibility, and the required confirmation step. Nothing needed to call it safely is missing.

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?

There is only one parameter (id) and schema description coverage is 100%, with the schema already stating where the id comes from (ragfeed_monitor_list or ragfeed_monitor_create). The description adds nothing further about the id, so the baseline 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 verb (delete) and resource (monitor) plus the cascade scope: all checks, results and stored page versions. It explicitly distinguishes itself from the narrower stop-only operation by naming ragfeed_monitor_update as the sibling for pausing.

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?

Gives an explicit when-to-use rule ('ask the user to confirm first') and an explicit when-not-to/alternative ('to stop it only for a while, pause it with ragfeed_monitor_update instead'). The agent can route correctly without opening any other schema.

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