install_custom_node

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

No annotations are provided, so the description carries the full burden. It mentions using the HTTP API (remote) and falling back to cm-cli (local), and notes that a restart may be required. However, it does not disclose potential side effects (e.g., overwrites, conflicts) or error behaviors.

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?

Three concise sentences cover purpose, method, and post-install action. No redundant phrases; information is front-loaded and well-structured.

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?

With 6 parameters and no output schema, the description covers core usage but is missing details on error handling, return value, or what happens when installation fails. The mention of restart is helpful but incomplete.

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 value by clarifying that 'id' accepts registry ids, git URLs, or names, and the 'useCmCli' forces subprocess. However, it does not add significant extra meaning beyond the schema's own descriptions.

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 it installs a ComfyUI custom node pack by registry id, git URL, or name. It distinguishes itself from sibling tools like 'update_custom_node' and 'fix_custom_node' by focusing on initial installation rather than updates or fixes.

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 some context (e.g., restart may be required, fallback to cm-cli), but does not explicitly state when to use this tool versus alternatives like 'reinstall_custom_node' or 'fix_custom_node'. The usage guidelines are implicit rather than explicit.

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