workflow_deps

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

No annotations are provided, so the description carries the full burden, and it does so thoroughly. It discloses that it is read-only, that nothing is installed or changed, that it wraps a ComfyUI-Manager call, what the return manifest looks like, and what happens when the required backend is absent.

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 dense but every sentence earns its place: purpose, wrapper, pipeline position, accepted inputs, return format, and key gotchas are all covered in a well-structured layout. The most important disambiguator (read-only mapping, not install) appears first, and the note about node_dependencies is explicitly isolated.

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?

Despite having no output schema and negligible parameter schema, the description provides the return manifest shape, identifies which keys feed install_node, flags repo URLs versus registry IDs, and explains the unsupported-backend failure. An agent has everything needed to call this tool correctly and interpret its result.

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 schema has 0% description coverage, but the description compensates by explaining exactly what workflow_path accepts: the same workflow JSON as run_workflow, or a .png with an embedded workflow. The parameter name plus the title further confirm it is a path, making the one required parameter fully usable.

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?

States a specific action and resource: maps workflow node classes to the node packs providing them. It also marks itself read-only, names the underlying command, and explicitly distinguishes itself from node_dependencies, so an agent can identify what it does.

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?

Gives an explicit pipeline: validate_workflow -> workflow_deps -> install_node -> restart_comfyui. It also states the alternative it is not (node_dependencies) and the prerequisites/failure mode (requires a ComfyUI-Manager comfy-cli can drive), leaving no ambiguity about when it applies.

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