connect_shader_nodes

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

There are no annotations, so the description carries the full burden of disclosing behavior. It only says 'connect', which implies a mutation, but it does not mention whether existing connections are replaced, whether nodes/sockets must already exist, or what happens on invalid socket names. For a mutating graph operation this is a meaningful transparency 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?

The description is compact and well-structured: one clear purpose sentence followed by a straightforward Args list. Every sentence earns its place, and the action is front-loaded before the parameter details.

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 simple operation, five clearly documented parameters, and no output schema, the description covers the essentials an agent needs to make the call: what the tool does, which material to target, and which nodes/sockets to connect. It does not explain edge cases like overwriting existing links, but that is secondary for a basic connect operation.

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 compensates by listing all five parameters with brief meanings: 'Target material', 'Source node name/label', 'Source socket name', 'Target node name/label', and 'Target socket name'. This adds basic semantics beyond the bare schema, though it stays shallow and gives no examples or constraints.

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 first sentence states a specific action and resource: 'Connect two shader nodes in a material's node tree.' This clearly distinguishes it from siblings like add_shader_node, set_shader_node_value, and connect_geometry_nodes by specifying both the operation and the domain (shader nodes, material node tree).

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 provides clear context: this tool connects shader nodes within a material's node tree, which implies it should be used after nodes exist and when a link is needed. It does not explicitly name alternatives or exclusion cases, but the domain restriction to 'shader nodes' and 'material's node tree' is enough to route an agent away from geometry-node or value-setting tools.

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