comfy_connect_nodes

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds only parameter labels and does not clarify whether the workflow is mutated in place or a new workflow is returned, nor whether connections are validated. This is a modest addition beyond the 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 description is a one-sentence purpose followed by a compact Args list. Every line earns its place and there is no filler or redundancy.

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?

With an output schema present and annotations covering safety, the description is mostly sufficient for a simple connection operation. However, it omits usage context and mutation semantics, which are important for a tool that manipulates workflow structure.

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 0%, but the Args section defines all five parameters with meaningful roles: workflow dictionary, source node ID, output index, target node ID, and target input name. This compensates well for the bare schema.

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 opening sentence 'Connect two nodes in a workflow' uses a specific verb and resource, clearly stating the tool's function. It is easily distinguished from sibling tools like comfy_add_node or comfy_set_widget_value.

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 gives no guidance on when to use this tool versus alternatives such as comfy_build_workflow, comfy_add_node, or comfy_validate_workflow. It also lacks any exclusions, prerequisites, or context about typical workflow-building sequences.

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