comfyui_clear_queue

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

The description discloses important behavioral details beyond the annotations, such as 'Stop the currently running workflow' for clear_running and 'Remove pending workflows' for clear_pending. This adds context about the destructive nature and the distinction between flags. It aligns with the destructiveHint and idempotentHint annotations, with no contradiction.

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 well-structured. It starts with a clear one-line summary, then provides a brief Args block. Every sentence is meaningful, and the formatting is clean, making it easy for an agent to parse.

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 queue-clearing tool, the description covers the core behavior and parameter effects. The presence of annotations (destructiveHint, idempotentHint) and an output schema reduces the burden on the description. It could mention return behavior or edge cases, but it is reasonably complete for the tool's simplicity.

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 schema has no descriptions for the parameters, but the description adds explicit semantics for both clear_running and clear_pending, explaining what each flag does. This is valuable beyond the schema's type and title information, making the tool's behavior clearer.

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 tool's purpose: 'Clear items from the execution queue.' This is a specific verb+resource combination that distinguishes it from sibling tools like get_queue or run_workflow. However, it does not explicitly differentiate from close siblings such as comfyui_interrupt or comfyui_cancel_job, which might also affect queue/running workflows.

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 provides no explicit guidance on when to use this tool versus alternatives like comfyui_cancel_job or comfyui_interrupt. There is no mention of prerequisites, suitable contexts, or exclusions. The usage is only implied by the tool's name and description.

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