blender_material_node_connect

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

With no annotations, the description carries the burden; it transparently states the core result ('creates a link') and its direction. It does not disclose whether an existing input connection is replaced, socket type compatibility, or failure behavior, so it is only minimally sufficient.

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 primary action and scoping material/shader graph appear first, and the link direction is clarified in the second sentence.

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?

Schema coverage is complete, but for a mutating graph operation with no annotations or output schema, the description omits useful context: valid socket discovery via inspect_graph, prerequisite node/material existence, and replacement semantics. It is adequate for basic invocation but not fully complete.

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?

Input schema already documents all five parameters at 100% coverage, so schema does the heavy lifting. Description adds only the output-to-input directionality, consistent with schema, but no extra formatting or value 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?

States a specific action: connect two nodes in a material's shader graph via socket names. Adds directionality (output-to-input), which clearly separates it from siblings like blender_material_node_add and blender_material_inspect_graph.

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 explicit when-to-use or alternatives; does not mention that the material and both nodes must already exist before linking. The only implied guidance is that this tool performs connections, so an agent would have to infer prerequisites from context.

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