set_shader_node_value

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

With no annotations available, the description carries the full behavioral burden. It discloses that it handles three value types (float, vector, color), which adds useful context, but it does not explain validation, side effects, error handling, or the return value (despite an output schema existing). It is a minimal contribution toward transparency.

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 extremely concise, consisting of two short sentences with no unnecessary words. The primary action and object are front-loaded, making it easy to scan.

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 four required parameters and no annotations, the description is inadequate. It fails to explain how to specify the value for different types, the purpose of each parameter, or what the output schema contains. An agent would lack critical details needed to reliably set a shader node input value, especially for vector or color inputs.

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 schema has 0% parameter description coverage, so the description must compensate. It does not explain the meaning of material_name, node_name, input_name, or value beyond the type hint implied by 'Handles float, vector, and color.' No parameter semantics are added, leaving the agent to guess how to format the value for each type.

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 clearly states the action ('Set') and the target resource ('default_value of a node input'). It also specifies the supported value types (float, vector, color), which distinguishes it from sibling tools like set_shader_node_property that set other node attributes.

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 guidance is provided on when to use this tool versus alternatives such as set_shader_node_property, connect_shader_nodes, or create_shader_node. There are no prerequisites, exclusions, or context hints to help an agent choose the appropriate tool.

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