blender_material_add_texture

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the basic action. It does not reveal whether the texture is added as a node in the material graph, whether it replaces existing connections, what happens if the image path is invalid, or what the default target input is when connect_to is omitted. For a mutation tool, this leaves important side effects undisclosed.

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 seven-word sentence with zero wasted words. It is concise, but the brevity borders on under-specification since it omits behavioral detail that would strengthen the agent's understanding.

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?

This is a mutation tool with no annotations and no output schema, so the description must compensate, but it is too sparse to do so. It does not explain the resulting material graph state, default connection behavior, prerequisite conditions (e.g., material must exist, image file must be accessible), or failure modes, leaving notable gaps for an agent deciding how to invoke it.

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 100%, so the schema already documents all three parameters (connect_to, image_path, material_name) with meaningful descriptions. The tool description adds no additional parameter-level detail, so the baseline of 3 is appropriate since the structured schema carries the weight.

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 states a specific verb ('Add'), a specific resource ('image texture'), and a target ('material'), making the core action clear. However, it does not differentiate itself from closely related siblings like blender_material_node_add or blender_ai_generate_texture, both of which could plausibly be used to bring a texture into a material.

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?

There is no guidance on when to use this tool versus alternatives such as blender_material_node_add, blender_material_set_principled, or blender_ai_generate_texture. No context is provided about scenarios where this tool is preferred, and no exclusions are mentioned.

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