blender_connect_shader

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

Annotations indicate a mutating, non-idempotent operation but do not explain what actually happens: whether existing connections are replaced, whether the material must already exist, or what side effects occur. The description adds only the direction of the connection and does not disclose behavioral traits beyond the implicit mutation.

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 a single, front-loaded sentence with no filler or redundant content. Every word contributes to the core action.

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 tool with five required identifier parameters and no output schema, this description is incomplete. It does not state what counts as a valid node/socket reference, whether the connection replaces or adds a link, or what a successful result looks like. An agent would likely need to infer too much to invoke it reliably.

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 only 17%, so the description must compensate. It does clarify that 'from_node'/'from_socket' represent the output side and 'to_node'/'to_socket' represent the input side. However, it does not explain how nodes or sockets are identified or how the 'material' parameter is resolved, leaving significant ambiguity.

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 ('Connect') and resource ('output socket to an input socket inside a material'), making the tool's core function clear. It does not explicitly differentiate from shader-related siblings like blender_set_shader_input or blender_build_shader, but the socket-connection action is distinct enough to infer.

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 alternatives such as blender_set_shader_input or blender_build_shader. The description implies it operates within an existing material's node tree, but gives no conditions, prerequisites, or exclusions.

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