install_comfyui

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

With no annotations, the description carries full burden and delivers: discloses it is synchronous, blocks, takes minutes, uses subprocess, creates venv, installs requirements and Manager (with fallback), and explicitly states it does NOT start ComfyUI. All behavioral traits are clearly communicated.

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 moderately long but well-structured with a summary first, then details. Every sentence adds important information; no fluff. Could be slightly more concise, but the density of useful information justifies the length.

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?

Despite no output schema in the structured field, the description provides a complete return JSON structure. It covers all behavioral aspects: synchronous nature, time requirement, never-overwrite policy, and Manager installation logic. Comprehensive for a complex tool.

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?

Schema coverage is 100%, but the description adds value beyond schema: clarifies version semantics (nightly/latest/semver, rejects raw git refs), explains fallback for use_uv, and summarizes skip_manager behavior. This enhances agent understanding without repetition.

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 installs ComfyUI locally with specific steps (git-clone, virtualenv, pip install). It distinguishes itself from sibling tools like 'install_custom_node' and 'update_comfyui' by specifying it is for fresh installations only and never overwrites an existing install.

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 clear context: target directory must be empty/non-existent, no overwriting, synchronous and time-consuming. However, it does not explicitly list alternatives or when-not-to-use scenarios, though the mention of 'never overwritten' implies not for updates.

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