set_shader_node_property

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

With no annotations, the description must convey behavioral traits, but it only states the action ('set') without disclosing side effects, failure modes, or requirements. It does not mention whether the property must already exist, whether existing connections are affected, or what the return value indicates. This is insufficient for a mutation tool.

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, front-loaded sentence with a clear verb and relevant examples. It is concise and easy to scan, but its brevity leaves out essential usage details. Given the lowness of content, it is efficient but not comprehensive.

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, no annotations, and no parameter descriptions, the description is grossly inadequate. It does not explain expected inputs, error behavior, or return values, and it fails to contextualize the tool's role among many shader-related siblings. An agent would likely need to probe or guess to use it 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 coverage is 0%, so the description must clarify parameters. It only elaborates on property_name by giving examples, but provides no insight into material_name, node_name, or value formats. The examples reduce ambiguity for one parameter, but the other three remain opaque, so compensation is partial.

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-object structure ('Set a property directly on a node') and provides concrete examples of properties (blend_type, operation, interpolation), which makes the purpose understandable. It does not explicitly differentiate from sibling tools like set_shader_node_value, but the examples signal it is about node properties rather than value inputs.

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 mention of prerequisites (e.g., material and node must exist), no exclusions, and no comparison with sibling tools such as set_shader_node_value or connect_shader_nodes. The description only implies a generic use case.

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