connect_shader_nodes

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

No annotations are present, so the description carries the full burden. It only discloses that sockets can be specified by name or index, but fails to mention side effects such as replacing an existing input connection, type compatibility validation, or error behavior when nodes/sockets are invalid.

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?

Two concise sentences, front-loaded with the primary purpose and no redundant information. Every word earns its place.

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 graph-mutation tool with no annotations, this description is minimal. It omits critical operational details like connection replacement semantics, compatibility requirements, and potential failure modes. The output schema exists but does not compensate for the lack of behavioral context.

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 coverage is 0%, but the description adds value by clarifying the anyOf types for from_output and to_input ('Sockets can be specified by name or index'). It also maps output/input to the parameter roles, though the remaining parameters are only clear by their names.

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 'Connect an output socket to an input socket,' specifying the precise action and resource. The tool name 'connect_shader_nodes' distinguishes it from sibling tools like 'connect_geonodes' and 'connect_comp_nodes', and the note about name/index adds useful specificity.

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 provided on when to use this tool versus alternatives (e.g., connect_geonodes). It does not mention prerequisites like material/node existence, nor does it explain whether connecting replaces existing connections.

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