set_node_input

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

The idempotentHint annotation already covers idempotency, and the description adds that the tool sets a default value rather than a current value, plus the allowed value types. However, it does not disclose potential side effects like whether setting a default value affects existing connections or whether it is limited to unconnected inputs.

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, direct sentence with no filler. It front-loads the verb and object, making the intent immediately clear despite its brevity.

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?

The description is too sparse for a 4-parameter tool in a large family of node-related tools. It does not specify which node tree type (shader, geo, compositor) it applies to, nor how to reference nodes and inputs. The idempotent annotation and presence of an output schema are helpful, but the missing operational context is significant.

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%, and the description only hints at the `value` parameter by naming supported types. It does not explain `material`, `node`, or `input` (including whether `input` is a socket name or index), leaving most parameter semantics underspecified.

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 resource ('node input's default value'), and it lists supported value types (color, float, vector), making the core purpose unambiguous. It distinguishes from sibling tools like get_node_input or set_node_position, though it does not explicitly name alternatives.

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_geonode_input, set_comp_node_input, or connect_shader_nodes. The description does not mention prerequisites or the node tree context it applies to.

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