comfy_validate_before_queue

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds value by specifying what is checked (VRAM headroom, queue depth) and what the return JSON includes (safe_to_queue flag, VRAM status, queue counts, issues), which enriches the agent's understanding without contradicting annotations.

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 front-loaded with the purpose. It uses bullets/headings for the return structure, making it scannable. No wasted words, though it could have explicitly mentioned 'does not modify state' but that's covered by annotations. Overall, efficient.

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?

The tool is simple (no parameters, straightforward output). With comprehensive annotations and a brief return description, the description is complete enough for an agent to understand what it does and what it returns. The output schema exists, so detailed return formatting isn't required here.

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, and schema coverage is 100% (vacuous). Per the rubric, 0 parameters sets a baseline of 4. The description doesn't need to add parameter info, and it doesn't.

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 a 'pre-flight safety check' checking VRAM headroom and queue depth before queueing a prompt. It uses specific verbs and resources, distinguishing it from similar tools like comfy_check_vram or comfy_get_queue by emphasizing its purpose as a pre-queue validation.

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 clearly indicates this is used before queueing a prompt ('Pre-flight safety check before queueing a prompt'), giving clear context. However, it does not explicitly mention alternatives or when not to use it, though among the many siblings, this is fairly obvious.

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