comfy_cancel_run

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

Annotations already indicate destructiveHint=true, but the description adds context that it affects 'running or queued' prompts, clarifying the scope beyond just 'cancel'. This adds behavioral detail not present in annotations alone, though it doesn't discuss irreversibility or effects on dependent operations.

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 extremely concise, with a clear first sentence stating the action and an Args section. No filler words, front-loaded with the main purpose. However, it is slightly sparse, lacking any additional usage context.

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?

Given the single parameter, output schema, and low complexity, the description is reasonably complete. It could mention that cancellation is permanent or what happens if the prompt is already finished, but overall it's adequate for a straightforward cancel operation.

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?

With 0% schema description coverage, the description provides a basic explanation for prompt_id ('The prompt ID to cancel'), adding minimal meaning beyond the schema. It clarifies the parameter's purpose but lacks detail about format or how to obtain the 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 explicitly states 'Cancel a running or queued prompt by ID', which is a specific verb+resource. It clearly distinguishes from similar sibling tools like comfy_cancel_jobs (jobs vs prompts) and comfy_interrupt (general interrupt vs specific prompt cancellation).

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 a specific prompt by ID but does not mention when to use it over alternatives like comfy_cancel_jobs or comfy_clear_queue. No explicit when-not-to-use guidance or contrast with sibling tools.

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