install_comfyui

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

With no annotations, the description fully carries the burden. It discloses that the tool is subprocess-only, synchronous, can take minutes, does not start ComfyUI, and returns a JSON report. This provides rich behavioral context beyond mere purpose.

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, well-structured paragraph that front-loads the main action. Every sentence adds value (installation steps, constraints, blocking, return format). It is slightly long but remains concise for the information provided.

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 4 parameters (all described) and no output schema, the description provides good context: it explains the required empty/non-existent target, manager installation, uv preference, version options, and the return JSON. It also explicitly states it does not start ComfyUI, which is important. Minor omission: no error handling details, but overall adequate.

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%, so baseline is 3. The description adds meaningful detail beyond the schema, such as the fallback for manager installation and version semantics (nightly, latest, semver). It enhances understanding of each parameter's behavior.

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 explicitly states 'Install ComfyUI locally' and details the process (git-clone, create virtualenv, install requirements). It distinguishes itself from sibling tools like install_custom_node by specifying the tool is for installing ComfyUI itself into a target directory.

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: local, subprocess-only, independent of remote, target must be empty or non-existent, synchronous, and can take minutes. It does not explicitly advise when to use this tool versus alternatives like update_comfyui, but the constraints are well-stated.

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