comfy_install_workflow_deps

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

Beyond annotations (which already indicate mutation, idempotency, and non-destructiveness), the description discloses the temp-file serialization, automatic cleanup, and default 600s timeout. It accurately reflects the operation without contradicting any annotations.

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 text is compact, front-loaded with the main action, and uses a clear 'Args:' section. Every sentence adds value—no filler or 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?

Given the two parameters, one nested object, and an output schema (which covers return values), the description fully describes behavior, including the long-running nature and timeout. It is complete for its complexity.

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?

The description adds critical meaning: workflow must be in API format, and workspace is an optional path passed to comfy-cli. This goes beyond the bare schema (which only says 'object' and 'string') and compensates for the 0% schema description coverage.

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 starts with a specific verb+resource: 'Auto-install every custom-node package the workflow references.' It clearly distinguishes from siblings like comfy_install_node by focusing on workflow-level dependencies. The wrapper command is named, adding precision.

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 implies usage for installing all dependencies referenced by a workflow, and notes it is long-running with a timeout. It does not explicitly list alternative tools or when not to use it, but the purpose is clear enough that an agent would know when this is appropriate.

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