connect_nodes

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

No annotations are provided, so the description carries the full burden, yet it discloses nothing about mutation semantics: whether an existing connection on the target input is replaced, whether types are validated (a separate check_compatibility tool hints they might not be), or what happens on an invalid node id or out-of-range output_idx.

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?

A single front-loaded sentence that names the action and both endpoints with no filler. It is efficient but under-specified rather than maximally informative for a 5-required-param mutation tool.

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?

For a write operation with no annotations, no output schema, and five required parameters, the description omits the essentials an agent needs: lifecycle ordering (create_workflow → add_node → connect_nodes → validate_workflow), overwrite behavior, and error conditions. The rich schema helps with parameter mechanics but not with correct invocation 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 100%, so all five parameters are already documented with examples (from_node e.g. "1", output_idx usually 0, input_name e.g. model/clip/positive). The description only restates the from/output-to/input mapping and adds no format or constraint detail beyond the schema, so baseline 3 applies.

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 verb (connect) and resource (an output of one node to an input of another) scoped to a dynamic workflow. An agent can tell it apart from add_node/remove_node, but there is no explicit differentiation from set_node_input, the nearest sibling for wiring values.

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?

No guidance on when to use this versus set_node_input or check_compatibility, and no prerequisites such as the workflow already existing (created via create_workflow) or both nodes already being added. The agent must infer the ordering from sibling names alone.

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