clear_queue

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

Description only states the action without disclosing side effects. As a destructive clearing operation, it does not warn about permanence or scope (e.g., impact on running jobs). With no annotations, the description carries full burden but fails to offer safety or behavioral context.

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?

Single sentence with no filler, effectively front-loading the verb and object. Every word earns its place.

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 0-param tool with an output schema, the description is close to adequate. However, it omits behavioral details like irreversibility and does not clarify its relationship to overlapping queue-management siblings, leaving a slight gap.

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?

Tool has zero parameters, and the empty schema means coverage is trivially 100%. The description adds nothing about parameters, but baseline for 0-param tools is 4 per rubric.

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?

Description uses specific verb 'clear' with resource 'all pending items from the ComfyUI queue', clearly distinguishing it from read-oriented siblings like get_queue. No ambiguity about the action or scope.

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?

No indication of when to use this tool versus alternatives like delete_queue_items or cancel_job. There are no usage conditions, prerequisites, or explicit exclusions provided.

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