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

With no annotations, the description carries the full behavioral burden. It explicitly discloses destructive side effects (deletes prompt, domains, results) and the non-refundable nature of unused runs, which is critical for a cancellation tool. It does not mention irreversibility or error behavior, but the destructive scope is clearly stated.

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 three short sentences that front-load the core action and side effects. 'Free.' is slightly extraneous, but the overall text is lean, scannable, and every other sentence contributes essential 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 simple one-parameter destructive tool with no output schema, the description covers the action, deleted resources, cost implications, and required id. It doesn't specify return format or error handling, but the simple input shape and absent output schema 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?

Schema description coverage is 100%: the monitor_id parameter is already fully documented (pattern, source from citation_tracker_monitor_7/_30, and credential status). The description merely restates 'Needs the monitor_id' without adding new semantic information, 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?

The description states a specific action ('Stops a monitor') and its precise destructive scope ('deletes its prompt, domains and results'). This clearly differentiates it from sibling tools like citation_tracker_monitor_7/_30 (creation) and citation_tracker_monitor_status (status checking).

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 usage is for canceling an existing monitor and warns 'Unused runs are not refunded,' but it does not explicitly say when to use this tool versus alternatives or what conditions would make cancellation inappropriate. No exclusions or alternative tool routing is provided.

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