connect_shader_nodes

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

There are no annotations provided, so the description carries the full burden of behavioral disclosure. It only states the action without mentioning side effects, requirements (e.g., existing nodes or materials), or failure behaviors. The phrase 'via their sockets' adds minimal insight, and no other behavioral traits are disclosed.

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, efficient sentence with no wasted words. It front-loads the core action and resource, making it easy to scan. However, its brevity borders on under-specification, though it is not redundant or verbose, so it merits a 4 for structure.

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 parameters and no parameter descriptions, this description is severely inadequate. It provides no information on how to reference nodes or sockets, whether they are names or indices, or any context about the shader node tree. Even with an output schema, the input semantics are completely undocumented, making it nearly impossible for an agent to call correctly without external knowledge.

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?

The input schema has 5 parameters with no descriptions (0% coverage), and the description does not explain any of them. The parameter names (material_name, from_node, from_socket, to_node, to_socket) give some hint of their intent, but there is no format, type, or reference information. The description adds almost no value beyond the schema's titles, leaving the agent to guess at valid values.

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 'Connect two shader nodes via their sockets' clearly states a specific verb and resource, and it distinguishes itself from the sibling tool 'disconnect_shader_nodes'. However, it lacks any additional context about the types of shader nodes or constraints, so it is clear but not detailed enough for a 5.

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 no guidance on when to use this tool versus alternatives like connect_gn_nodes or connect_compositor_nodes. It does not mention any prerequisites, exclusions, or situations where this tool is preferred. Without this, the agent cannot reliably select it from the many similar connection tools.

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