comfyui_clear_queue

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Remove pending workflows' states the basic action, it does not mention that the operation is destructive and irreversible, nor that it only affects pending workflows and not the currently running one. This lack of safety-related context is a notable gap for a clear-queue operation.

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 redundant words. It communicates the essential action directly and efficiently.

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 zero-parameter tool with an output schema, the description covers the core behavior adequately. It could add a note about the complete/irreversible nature, but 'pending' already implies non-running workflows, so the context is mostly 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?

The tool has zero parameters, so there is no semantic burden on the description. The schema coverage is effectively 100%, and the baseline for 0 parameters is 4, which is appropriate here since no parameter explanation is needed.

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 verb 'Remove' and the resource 'pending workflows from the ComfyUI queue', which precisely conveys the tool's action. It also distinguishes itself from sibling tools like comfyui_interrupt by specifying 'pending' workflows rather than running ones.

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?

There is no guidance on when to use this tool versus alternatives such as comfyui_get_queue (to view the queue) or comfyui_interrupt (to stop running workflows). The usage context is only implied by the tool name and description, with no explicit exclusions or prerequisites.

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