create_image_texture_node

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

With no annotations, the description must disclose all behavioral traits. It does reveal a key behavior: for role='normal', the image is set to Non-Color and routed through a Normal Map node. However, it omits other important behaviors such as whether existing connections are overridden, whether the material must already contain a Principled BSDF, what happens if both image and filepath are supplied, or what the function returns. The provided detail adds some value beyond the schema, but significant gaps remain.

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 compact and well-structured, leading with the core purpose in the first sentence, then providing the most critical usage details (image vs filepath, role='normal') in a brief second paragraph. Every sentence carries information without waste, making it easy for an agent to parse quickly.

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's complexity (10 parameters, no output schema), the description is far too sparse. It does not cover the meaning or effect of several parameters, does not describe error conditions, preconditions (e.g., material existence), or post-conditions (e.g., where the node is placed in the node tree). The description provides only a fraction of what an agent would need to use the tool correctly across its full parameter space.

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 60%, so the description should compensate for undocumented parameters. It does add meaningful semantics for the image/filepath choice (mutual exclusivity) and the role='normal' effect on color space and node routing. However, it does not elaborate on parameters like name, location, extension, or interpolation, which remain undocumented in both schema and description. The added value is real but partial, falling short of compensating for the coverage gap.

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 ('Add an Image Texture node') and the resource ('wire it into the material'), making the tool's purpose unambiguous. It also distinguishes itself from generic sibling tools like create_node by specifying the node type and the special handling for normal maps, so an agent can immediately tell when this tool is the right choice.

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 does not explicitly state when to use this tool versus alternatives such as create_node, set_node_inputs, or load_image. It only provides guidance on parameter choices (image vs filepath) and the role='normal' special case, but no exclusions or alternative routing. An agent is left to infer the tool's applicability from its purpose, which is insufficient given the many related siblings.

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