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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the description's added value is in the specifics: the uploaded input is deleted and a live worker aborts its subprocess and throws away partial measurements. That is meaningful disclosure beyond the annotation. It does not address what a repeat call on an already-cancelled or already-completed task returns, which matters given idempotentHint=false.

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?

Three tight sentences ordered as action, side effect on the worker, then safety boundary. Every sentence carries distinct information and the destructive outcome is front-loaded.

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 one-parameter mutation with an output schema covering return values, the description covers the essential behavior: what is deleted, what the worker does, and what is out of scope. The remaining gap is the absence of any statement about the identifier's provenance and repeat-call behavior, consistent with idempotentHint=false.

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?

The single parameter task_id has 0% schema description coverage, so the description must carry the burden, and it does not mention task_id at all. It never says where the identifier comes from (presumably the render upload/creation step) or that it must reference an existing analysis owned by the caller, leaving only the pattern and length constraints from the schema.

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 and resource ("Cancel your private render analysis") plus a second concrete effect ("remove its uploaded input"). No sibling tool performs cancellation, and the scoping words "your private" separate it from any catalogue-level operation.

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 makes clear the target must be the caller's own render analysis and explicitly rules out acting on another account's task or a catalogue video, which is real when-to-use context. It stops short of naming what to do instead if the caller actually wants to keep the input or re-run the analysis, so no alternative routing is offered.

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