set_node_image

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the core action (pointing a node at a different image) but does not disclose side effects, error conditions (e.g., node not found, invalid image), or whether the operation is reversible. For a mutation tool with zero annotation coverage, this is a significant gap.

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 no filler. It immediately states the action and the object being modified. Perfectly concise and well-structured.

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?

Given the tool has three required parameters and no output schema or annotations, the one-sentence description is insufficient. It does not explain return values, error handling, or preconditions (e.g., whether the node must already be an Image Texture node). For a mutation tool with zero schema coverage, an agent lacks the information needed to call it correctly without additional investigation.

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 explain the parameters. It mentions 'node' and 'image' implicitly, but the 'material' parameter is never addressed. The description does not clarify which node type is expected, what format the image identifier takes, or how the material parameter is used. It fails to compensate for the schema's lack of detail.

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 ('point') and resource ('existing Image Texture node') to clearly state the operation. It distinguishes itself from siblings like create_image_texture_node (which creates a new node) and set_node_inputs (which generically sets inputs). An agent can immediately understand what this tool does without opening the schema.

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 description implies the tool is for modifying an existing node, contrasting with creation tools, but it does not explicitly name alternatives or state when-not to use it. There is no guidance about prerequisites (e.g., the node must already exist) or when to choose this over set_node_inputs. The context is clear but lacks explicit routing.

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