Connect two nodes

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

Annotations already indicate a non-read-only, non-destructive operation. The description adds valuable behavioral context by disclosing the fallback mechanism ('Uses the bridge's batch endpoint when available and falls back to a Python connect otherwise') and what is returned, without contradicting 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?

Three sentences, front-loaded with the core action, followed by fallback behavior, alternative usage, and return info. Every sentence earns its place with no 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?

Covers the operation, fallback behavior, return values, and an explicit alternative. With full parameter schema coverage and annotations, this is sufficient for a simple 4-parameter tool, though it could mention edge cases like occupied connectors but that is not essential.

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%, with each parameter already described. The description does not add extra parameter semantics beyond the schema, though it does mention connector indices in the return context, which slightly reinforces their purpose. Baseline of 3 is appropriate.

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 specific action: 'Wire one node's output connector into another node's input connector inside TouchDesigner, creating a single link between two existing nodes.' It names the verb, resource, and scope, and distinguishes from siblings like create_node_chain and disconnect_nodes.

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?

Explicitly says when to use an alternative: 'Use create_node_chain instead when you are creating several new nodes and want them auto-wired in sequence.' Also implies it's for connecting existing nodes, giving clear context and an exclusion.

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