shading-add_image_texture

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

No annotations are provided, so the description must carry the transparency burden. It only states the high-level action without disclosing side effects, such as creating new nodes, replacing existing connections, or requiring a pre-existing material. It also does not mention anything about image loading behavior or UV setup, leaving significant behavioral ambiguity.

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 sentence with no fluff. Every word contributes to the core purpose, making it highly concise and easy to parse.

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 tool that creates and wires nodes, the description is underspecified. It does not explain prerequisites (e.g., whether a material must exist), the effect on existing node connections, or the meaning of the 'target' choices beyond the enum values. Given the complexity of shading operations, this is incomplete.

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%, but the schema provides titles for all three parameters. The description adds only conceptual context ('image-texture node', 'Principled BSDF target') without explaining parameter meanings or relationships beyond what the schema already states. It does not compensate for the lack of schema descriptions.

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 ('wire') and identifies the resource ('an image-texture node to a Principled BSDF target'). It clearly distinguishes from sibling tools like shading-add_node or shading-link_nodes by implying a higher-level composite action for adding and connecting an image texture.

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 a use case (adding an image texture to a PBR input) but provides no explicit when-to-use or alternatives. It does not mention when to prefer this over lower-level tools like shading-add_node and shading-link_nodes, leaving the agent to infer based on naming.

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