set_node_input

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

The description adds that the operation changes the default value rather than a connected/current value, and it hints at the accepted value shapes. The idempotentHint annotation already covers repeatability; side effects on existing connections or material dependencies are not mentioned, but nothing contradicts the annotation.

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?

A single focused sentence with no filler or redundant schema repetition. The verb, target, and value types are front-loaded.

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 four-required-parameter mutation tool with zero schema descriptions, this is too thin. An agent cannot tell which node domain this tool applies to, how `input` is identified, or what value array formats are expected. The output schema covers return shape, but not selection or invocation details.

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?

With 0% schema description coverage, the description partially compensates: it clarifies that `value` can be a color, float, or vector, and the phrase 'node input' gives meaning to the `input` parameter. It does not explain whether `input` is a name or index, nor what formats `node` and `material` expect.

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 states a clear action ('Set') and object ('a node input's default value') and enumerates the accepted value kinds (color, float, vector). It does not explicitly distinguish this from sibling tools like set_geonode_input or set_comp_node_input, so it is not a perfect 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?

There is no guidance about when to use this tool versus get_node_input, set_node_position, or the domain-specific input setters. No prerequisites, call order, or alternative selection cues are provided.

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