connect_shader_nodes

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It usefully reveals that sockets can be addressed by name or index, but it does not disclose what happens to an existing connection on the target input (Blender inputs accept a single connection, so this likely replaces it), nor does it mention validation of socket types or error behavior. For a mutating tool this is a significant gap.

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 sentences with no filler; the core action is front-loaded and the second sentence adds genuinely useful parameter semantics. 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 5-parameter graph-editing mutation with zero annotations and zero schema descriptions, the description is thin. It omits node/material reference semantics, the replacement behavior on existing connections, and any guidance on resolving socket type mismatches. The presence of an output schema mitigates return-value ambiguity, but input-side semantics remain under-specified.

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% for all 5 parameters, so the description must compensate. It explains the string-or-integer socket variants ('by name or index'), which maps to from_output and to_input, but it leaves material, from_node, and to_node semantics to inference from their names, and does not explain how nodes or materials are identified or how directionality is encoded.

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 ('Connect an output socket to an input socket') with a clear direction of data flow. The tool name carries the 'shader' scope, distinguishing it from connect_geonodes and connect_comp_nodes, though the description itself does not explicitly name this differentiation.

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?

There is no guidance on when to use this tool versus its close alternatives (connect_geonodes, connect_comp_nodes, disconnect_shader_node, set_node_input). No context is given about prerequisites such as the material existing or the nodes being present in the tree, and no exclusions are stated.

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