install_node_pack

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

With no annotations, the description fully discloses the behavior: queues, starts, polls, requires restart, and fails on security blocks. Mentions trust and safety, providing clear expectations for the agent.

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?

Two concise sentences plus a brief note; every sentence adds value. Front-loaded with core action and key constraint, then details the process and post-condition.

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?

Covers the full workflow: queueing, polling, restart requirement, and error handling. Output schema exists, so return value explanation is unnecessary. Complete for an agent to use 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?

Explains pack_id as the registry id from find_missing_nodes, but does not clarify the version parameter (its default 'latest' is only in schema). Schema coverage is 0%, so description partially compensates but leaves a gap.

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?

Clearly states the tool installs a custom-node pack using its ComfyUI-Manager registry id, specifying the source as 'trusted registry' and referencing find_missing_nodes for the id. Distinguishes from sibling tools like install_model and find_missing_nodes.

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?

Indicates the tool should be used for trusted registry packs, mentions the prerequisite of obtaining the id from find_missing_nodes, and advises a subsequent restart via restart_comfyui. Does not explicitly state when not to use, but the context implies avoidance for arbitrary code.

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