connect_shader_nodes

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

The description adds no behavioral details beyond the name itself. While annotations already indicate destructive behavior, the description does not disclose whether existing connections are overwritten, whether type mismatches are handled, or any side effects. With annotations present, the bar is lower, but the description still provides minimal added value.

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 only one sentence, which is concise and free of fluff. However, it is so brief that it under-specifies a tool with five required parameters. While conciseness is valued, substantial content is missing, so it earns a middle score.

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?

With five parameters and no schema descriptions, the tool is under-documented. The description does not explain the function's purpose in context, such as what materials or nodes are eligible, nor does it mention any return values or error conditions. Despite having an output schema, the description remains incomplete.

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%, so the description must compensate. However, it does not explain any parameter's meaning or relationships. The parameter names are somewhat self-evident, but the description adds no guidance on how to fill them, such as expected socket naming conventions or node identifiers.

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 uses a clear verb 'connect' and identifies the resource as 'shader node sockets', which distinguishes it from sibling tools like adding or removing nodes. However, it does not explicitly state that it connects an output to an input, which could be ambiguous. Overall, it provides a clear purpose.

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, no prerequisites, and no exclusions. The description is a single imperative sentence with no contextual direction. Sibling tools like add_shader_node or set_node_value are not mentioned.

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