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

Annotations already declare destructiveHint=true and openWorldHint=false, so the safety bar is partly covered, but the description adds real value: the run cancels only at its next safe point, and the schedule is paused rather than deleted. 'Safe to repeat' sits in mild tension with idempotentHint=false (harmless repeat vs. identical effect), though it does not directly contradict it.

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 its effect, followed by the recovery path. No filler or restated name/title.

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 destructive, non-idempotent mutation with no output schema, the description covers what changes (schedule paused, run canceled at safe point) and how to undo it. It omits what the call returns and what happens to run history, a minor gap given the small 3-param schema.

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 coverage is 100%, so agent_id, task_id, and note are fully documented in the schema itself. The description adds no parameter-level meaning (e.g., what the optional note is for), so the baseline 3 is appropriate.

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?

Specific verb+resource (stop a task) with concrete scope: it pauses the schedule and cancels the in-progress run. It is distinguishable from siblings like cancel_agent_run or archive_agent_task by the schedule-pause detail, though it doesn't explicitly contrast itself with them.

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?

Says 'Stop a task now' and gives the reversal path ('Resume it later with update_agent_task status active'), which is clear usage context. It stops short of explicit when-not guidance or naming when cancel_agent_run or archive_agent_task would be the better pick.

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