comfyui_install_custom_node

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

The description details key behaviors beyond annotations: the restart option triggers a security audit, and if False a manual restart is needed. It also explains the return value includes audit results when restart=True. This significantly increases transparency for a mutation tool.

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 well-structured with purpose, Args, and Returns sections. Every line provides meaningful guidance, and the format is easy to parse. No unnecessary repetition.

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 tool with 3 parameters, an output schema, and annotations, the description is complete. It covers the action, parameters, behavioral differences, and return format, leaving no critical gaps for an agent to select and invoke it correctly.

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 parameters are well-documented already. The description adds extra value by pointing to search_custom_nodes for node_id discovery and clarifying the consequence of restart=False, going beyond the schema's 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 the tool installs a custom node pack from the ComfyUI Manager registry, using a specific verb and resource. It distinguishes from siblings like uninstall/update by naming the 'install' action and registry source.

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 for when to use the tool (installing from registry) and even references 'use search_custom_nodes to find IDs' as a prerequisite. However, it doesn't explicitly mention alternatives or when-not conditions, though the purpose statement is sufficient for basic selection.

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