comfyui_manage_queue

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description confirms destructive behavior but does not add new behavioral context (e.g., irreversibility, permissions required). Since annotations cover the safety profile, the description adds minimal extra transparency.

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 sentence with no wasted words. It efficiently communicates the tool's purpose and action. Ideal conciseness for a tool with clear semantics.

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 tool's moderate complexity (two actions in one endpoint), the presence of annotations, output schema, and detailed parameter schemas, the description is mostly complete. It could mention that actions are destructive or irreversible, but annotations already flag destructiveness. No major gaps.

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 input schema already contains parameter descriptions (clear: 'If true, clears all pending queue items.'; delete_prompt_ids: 'Specific prompt IDs to delete from pending queue.'). With 100% schema description coverage, the tool description does not add additional parameter meaning; baseline 3 is appropriate.

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 performs two actions: clearing the queue or deleting pending prompt IDs, and specifies the HTTP method and endpoint. This distinguishes it from sibling tools like comfyui_get_queue (read-only) and comfyui_interrupt (interrupting running 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 contexts (clearing vs. deleting specific IDs) but does not provide explicit guidance on when to choose one over the other or when to use this tool instead of siblings. No exclusions or alternatives are mentioned.

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