blender_load_image_texture

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

Annotations indicate a mutating, non-idempotent operation, but the description adds useful behavior: it auto-creates a material if none is named and supports .hdr/.exr files. However, it omits other potential side effects, such as whether existing base color nodes are overwritten or how the image is registered in Blender. These gaps are significant given the tool's mutation nature.

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 concise, with the primary action and key constraint front-loaded. It avoids fluff and wastes no words. However, it could be slightly more structured to add missing details without becoming verbose, so it is not a perfect 5.

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 mutating tool with low schema coverage, no output schema, and no annotation details beyond high-level flags, the description leaves out critical context: what happens to an existing material, how the agent should interpret the response, and any prerequisites. The description is not sufficient for an agent to safely and correctly invoke the tool in all reasonable scenarios.

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 only 33% (only response_format has a description). The tool description offers only a minimal hint for the 'material' parameter ('if you do not name one') and implies 'path' is a disk file, but does not clarify path syntax (absolute/relative), file resolution, or the meaning of 'response_format'. Since the schema fails to describe most parameters, the description should compensate, but it does not.

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 ('Load an image from disk') and the target ('plug it into a material as Base Color'), and specifies the file formats supported (.hdr/.exr). It also notes material auto-creation, which distinguishes it from related tools like blender_create_material or blender_assign_material. This makes the tool's purpose unambiguous.

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 when to use the tool (when you need to set a base color from an image file) but does not explicitly contrast it with alternatives like blender_generate_texture or blender_set_material_node. No 'when not to use' or direct sibling comparisons are given, leaving some ambiguity for an agent deciding between tools.

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