set_shader_node_input

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

With no annotations provided, the description carries the burden and discloses meaningful behavior: only unconnected sockets are affected, linked sockets ignore defaults, and a link must be removed first. It also documents the return shape, though it omits error behavior and permission requirements.

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?

Front-loads purpose and key link caveat, then uses structured Args and Returns sections. Every sentence adds useful information without repetition or filler.

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 4-parameter mutation tool with no annotations and 0% schema description coverage, the description supplies the missing parameter semantics and critical behavior. An output schema exists, so return values need not be explained further, making the definition complete enough to invoke correctly.

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 and does: it explains material_name, node_name, socket as name or zero-based index with an ambiguity example (Math node 'Value'), and value as number, boolean, or 2-4 component list including RGBA colors.

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 verb ('Set') and resource ('default value of an unconnected input socket on a shader node'), and the scope ('unconnected') clearly distinguishes it from connect_shader_nodes, disconnect_shader_nodes, and set_shader_node_property.

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?

Gives clear context for when to use it ('dial in a procedural texture') and a prerequisite ('disconnect it first if you want the default to take effect'), but does not name explicit alternatives such as set_shader_node_property or when not to use this tool.

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