install_workflow_dependencies

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

With no annotations, the description takes full burden. It discloses server-side execution via ComfyUI-Manager, local or remote target support, the multi-step process, and the required restart. It doesn't detail error handling or idempotency, but covers the essential behavioral traits adequately.

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 four sentences with clear front-loading of the main purpose. It is concise without being terse, but could be slightly more structured (e.g., bullet points for steps). Still, every sentence adds value.

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 the multi-step operation and no output schema, the description explains what is reported (installed/already-present/unresolved) and the need for a restart. It lacks error handling details but is otherwise complete for an agent to understand the tool's role.

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 description coverage is 100% (the single parameter 'workflow' is already described as 'ComfyUI workflow in API format'). The tool description adds no additional semantics beyond that, so baseline 3 is appropriate.

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 the verb 'Resolve and install' with the resource 'custom node packs a ComfyUI workflow requires via ComfyUI-Manager.' It details each step (determines missing packs, resets queue, queues installs, runs worker, reports results), distinguishing it from siblings like extract_workflow_dependencies and install_custom_node.

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 context on when to use (to install dependencies from a workflow) and mentions it mirrors comfy-cli node install-deps, but does not explicitly contrast with alternatives like sync_node_dependencies or list installed nodes. It states the typical need for a ComfyUI restart, which helps set expectations.

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