connect_comp_nodes

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

There are no annotations, so the description must disclose behavior. It does not explain side effects, whether existing connections are overwritten, how sockets are matched, or any other behavioral traits beyond the bare word 'connect'.

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 extremely short but under-specified. A single sentence that merely restates the tool name is not effective conciseness; it lacks the detail needed to be useful.

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 tool has four required parameters, no annotations, and an output schema that is not elaborated. The one-sentence description is grossly insufficient for an agent to understand how to connect compositor nodes correctly.

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 schema defines four required parameters with zero description coverage. The description does not explain from_node, from_output, to_node, or to_input, leaving the agent unable to infer what values to provide or the relationship between them.

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 'Connect compositor nodes.' essentially restates the tool name connect_comp_nodes. It names a verb and resource but provides no additional clarity about what 'connect' entails or what distinguishes it from shader or geometry node connection tools.

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 is given on when to use this tool versus alternatives like connect_shader_nodes or connect_geonodes. It does not mention context, prerequisites, or exclusions.

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