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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, but the description still adds meaningful behavior: completed images are preserved, batch cancellations refund ungenerated images, and a race (batch finishing first) yields full retention. The refund explanation is somewhat convoluted ('Other tasks are never charged for the rest'), which keeps it below 5.

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 first sentence is front-loaded and effective, but the middle refund/batch sentences are dense and ambiguous ('the cancel is sent to the picture maker', 'Other tasks are never charged for the rest'), costing clarity for a single-param tool.

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?

No output schema exists, and the description covers the return value (saved vs requested image counts) as well as side effects on already-generated assets and billing. An agent has enough to call it and interpret the result, though the race-condition wording could be crisper.

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% with a single required taskId that is already documented with its source tools. The description adds no extra format or provenance detail beyond the schema, 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 (stop/cancel) and resource (one of your generation tasks) with explicit scope: queued AND running tasks. That scope distinguishes it from the sibling cancel tools (cancel_editor_run, aftereffects_cancel_edit, premiere_cancel_edit), which target editor jobs rather than generation tasks.

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?

Scoping to 'generation tasks' implies it is not for editor runs, and the schema points to task ids from generate_image or list_generations. But there is no explicit when-to-use/when-not sentence naming an alternative, so the routing is left to inference.

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