comfyui_interrupt

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only restates the tool's name/action without explaining side effects, idempotency, what happens to queued workflows, or whether it is a no-op when nothing is running.

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 a single, front-loaded sentence with no wasted words. It states exactly what the tool does without extraneous detail.

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?

This is a simple zero-argument action tool, and the description sufficiently identifies the target and action. The output schema exists, so return values need not be explained. However, a brief note on side effects or relation to the queue would make it more robust.

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 tool has zero parameters, so the parameter semantics baseline is 4. No parameter descriptions are needed, and the empty schema is consistent with the tool's purpose.

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 uses a specific verb ('Interrupt') and a specific resource ('the workflow currently executing in ComfyUI'), which clearly distinguishes this from sibling tools like comfyui_clear_queue (queue-level) and comfyui_run_workflow (starting execution).

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 phrase 'currently executing' implies this tool should be used when a workflow is running, providing some usage context. However, it does not explicitly mention alternatives, exclusions, or when not to use it, such as for clearing the entire queue.

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