Connect two nodes

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

The description mentions using a batch endpoint with a Python fallback, which is a behavioral detail beyond annotations. However, it does not disclose other traits like side effects, permission requirements, or handling of existing connections.

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 two sentences, efficiently conveying the core purpose and a key technical detail. No unnecessary 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 the complexity of connecting nodes (4 parameters, no output schema), the description lacks important context such as behavior on existing connections, error conditions, or supported node types.

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?

The input schema has 50% coverage (only source_path and target_path have descriptions). The description does not add any clarification for the undocumented parameters (source_output, target_input), failing to compensate for the gap.

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 action: 'Wire one node's output into another node's input.' It distinguishes from sibling tools like 'compare_td_nodes' or 'animate_parameter' which have different purposes.

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 does not provide guidance on when to use this tool versus alternatives. No mention of prerequisites, conditions, or when not to use it.

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