set_node_inputs

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It states the core effect and the 'unlinked' scope, but it does not say whether existing default values are overwritten, whether the operation is reversible, what errors may occur, or what the response looks like.

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 concise, front-loaded sentence that clearly conveys the action, target, and keying structure without fluff. Every word earns its place.

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?

With no output schema, no annotations, and a nested 'inputs' object, the description is minimal but arguably sufficient for a straightforward setter. It explains what is being set and how the inputs map is keyed, but it does not cover error handling, prerequisites, or what happens to linked sockets.

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. It adds meaning to 'inputs' by specifying they are keyed by socket name, but it says nothing about the value types or how 'material' and 'node' identifiers should be resolved. This is partial compensation, not complete.

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 specific verb and resource: 'Set default values on a node's unlinked input sockets, keyed by socket name.' This clearly distinguishes it from sibling tools like connect_nodes, which create wiring, and set_node_image, which sets a specific image input.

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?

The phrase 'unlinked input sockets' implies that this tool is for assigning defaults to disconnected inputs, which provides some usage context. However, it does not explicitly contrast this with alternatives such as connect_nodes or mention what happens if a socket is already linked, so the guidance is mostly implied rather than explicit.

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