comfyui_cancel_download

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

Annotations already signal destructive behavior (destructiveHint=true), and the description adds the phrase 'and remove,' clarifying that the task is deleted. However, it doesn't disclose side effects like whether partial downloads are deleted or if the action is irreversible, so it adds only marginal context beyond annotations.

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 concise and front-loaded with the action, but the docstring format is rather minimal. It earns its place without verbose explanations, though it could be slightly more structured with clearer separation of purpose and parameters.

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 tool with one parameter and an output schema, the description is adequate but lacks guidance on when to use it and what happens to the underlying download files. It doesn't address edge cases like canceling a completed or already-canceled task, making it only minimally complete.

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 0%, but the description provides a clear docstring for task_id, stating it is the ID of the download task to cancel. This adds meaningful context over the schema's bare 'Task Id' label, though it could be even more explicit about where to find this ID.

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 clearly states the action ('Cancel') and the resource ('model download task'), and uses the verb 'remove' to add specificity. It distinguishes itself from sibling tools like comfyui_cancel_job, which targets jobs rather than download 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?

The description implies usage for canceling model downloads but does not explicitly mention when to use it instead of alternatives like comfyui_cancel_job. There is no exclusions or comparison, so the guidance is implied rather than explicit.

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