connect_comp_nodes

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'connect', with no details about whether existing input connections are replaced, whether socket types must match, what happens on failure, or whether the operation is reversible. The behavior beyond the bare action is not disclosed.

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 very short and front-loaded, but it is under-specified for a tool with four required parameters and no parameter documentation. It is concise without being wasteful, but the brevity crosses into missing useful context.

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 connection operation with four required parameters, no annotations, and no parameter descriptions, a three-word description is insufficient. An agent would need to know how to identify outputs/inputs, whether nodes must already exist, and the semantics of string versus integer socket references.

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%, and the description does not compensate by explaining the four required parameters. While names like from_node and to_node are self-explanatory, from_output and to_input are ambiguous between socket names and indices, and the description provides no clarification.

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 states a specific verb and resource: connecting compositor nodes. It is not a tautology, and 'compositor' clearly distinguishes this from sibling tools like connect_shader_nodes and connect_geonodes, though it does not explicitly name those alternatives.

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 gives no guidance on when to use this tool versus connecting shader or geometry nodes, nor does it mention prerequisites like existing nodes or compatible socket types. Usage is only implicitly tied to compositor nodes by the description itself.

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