connect_nodes

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

Despite no annotations, the description discloses key behavioral traits: connecting replaces existing connections on the input port, and for certain nodes (like Combine) the Method property must be set first. However, it does not mention whether changes are immediately persisted or reversible, but the core behavior is transparent.

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 concise at 5 sentences, well-structured with a clear progression: purpose, default usage, special cases, and important constraint. No redundant 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?

The description covers the action and important nuances but lacks information about return values or post-call state. Given no output schema and the tool's nature (mutation), completeness could be improved by mentioning what happens after connection (e.g., the graph is updated) or verifying nodes exist. However, it is fairly complete for a connect operation.

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?

With 100% schema coverage, the baseline is 3. The description enhances parameter understanding by explaining default port values ('Out' → 'In'), giving concrete examples for nodes with multiple ports, and tying the filename parameter to a .terrain file. This adds value beyond the schema definitions.

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 clearly states the tool connects two nodes by wiring an output port to an input port, with explicit default ports and examples for nodes with multiple ports. It distinguishes itself from siblings like 'disconnect_port' by focusing on connection, not disconnection.

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 provides explicit guidance on when to use default ports, how to specify port names for multi-port nodes (e.g., Combine, Erosion2), and the prerequisite of setting the Method property for Combine nodes before connecting. It also warns that each input port accepts only one connection and connecting replaces existing ones.

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