comfyui_connect_nodes

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the core connect action and does not reveal what happens if the target input already has a connection, whether the revision parameter is enforced, or what validation is performed. This leaves significant behavioral ambiguity for a mutation tool.

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 single sentence that is instantly scannable and front-loads the primary action. Every word contributes to meaning, with no filler or repetition of schema information.

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 six parameters and no annotations, the description is too sparse to be fully actionable. It fails to mention important behavioral details such as whether existing connections are overwritten, how expected_revision affects execution, or potential failure modes. The output schema exists but does not substitute for missing usage context.

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%, so the description must compensate for undefined parameters. It clarifies that source_output is an index and target_input is named, but it leaves workflow_name, expected_revision, and the exact meaning of source_node/target_node unexplained. The description adds minimal value beyond the parameter names themselves.

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 uses a specific action verb ('connect') and identifies the precise resource ('one node output index to a named input on another node'). This clearly distinguishes it from siblings like comfyui_disconnect_input, which performs the opposite operation.

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 wiring nodes together, but it does not explicitly state when to use this tool versus alternatives like set_input or disconnect_input. It lacks a when/when-not comparison, instead relying on the tool name and context to convey its role.

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