material_set_texture

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

No annotations provided. The description does not disclose behavioral traits: whether it replaces existing textures, if a Principled BSDF node is created automatically, or dependencies. The single action 'Add' is vague regarding side effects. With no annotations, the description fails to provide sufficient behavioral context.

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?

Description is concise: one main sentence plus parameter list in docstring format. No unnecessary words. However, the parameter list uses extra whitespace and could be tighter. Still, it's efficient and front-loaded.

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?

No output schema, and description does not mention return values. Given the tool's simplicity (3 parameters, clearly defined), it is minimally complete but lacks details like file path validation, behavior with non-existing materials, and whether multiple textures can be added. For a straightforward operation, it's adequate but not rich.

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 coverage is 0%, so description carries burden. It adds meaning to texture_type by listing four valid options with descriptions (base_color: Albedo/diffuse, etc.), which is helpful. For material_name and texture_path, it merely restates names, offering minimal extra value beyond schema titles. Overall, partial semantic support.

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 tool adds an image texture to a material's Principled BSDF. The verb 'add' and resource 'image texture to material's Principled BSDF' are specific, and it distinguishes from sibling tools like set_material_color or set_texture, which may not target Principled BSDF directly.

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 on when to use this tool versus alternatives like set_texture or set_principled_bsdf. Missing prerequisites such as material existence or valid texture path. The description does not mention when to choose this over other material editing tools.

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