Apply an image texture to a Blender object by specifying the image file path and optionally an existing material. Ideal for quick texture assignment in automated workflows.
Apply an image texture to an object.
Args: object_name: Target object. image_path: Path to the image file. material_name: Optional existing material to add texture to.
| Name | Required | Description | Default |
|---|---|---|---|
| image_path | Yes | ||
| object_name | Yes | ||
| material_name | No |
Changes observed during successful MCP inspections.
v3.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the basic action but does not explain side effects, whether a new material is created, whether an existing material is overwritten, what happens if the image path is invalid, or what the tool returns. The material_name argument hints at some behavior but leaves key details implicit.
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 short and front-loaded with the core purpose. The argument list is compact and follows the schema closely without unnecessary filler. It could be slightly more informative, but it stays concise and scannable.
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 no annotations, no output schema, and a large sibling set, the description is under-specified. It omits important context for correct invocation: whether UV mapping is required, whether a fallback material is created, how material_name interacts with existing materials, and what success or failure looks like. The tool is simple but still needs more behavioral context.
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%, so the description must compensate. It does provide brief explanations for all three parameters: object_name, image_path, and material_name. These add meaning beyond the bare schema titles, but the explanations are minimal and lack useful constraints such as supported image formats, path expectations, or material-name resolution behavior.
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 operation: 'Apply an image texture to an object.' It names a specific verb, resource, and target. It is clear enough to be understood, but it does not explicitly distinguish itself from nearby material-related siblings like create_procedural_material or assign_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 about when to use this tool versus alternatives. It does not mention prerequisites, common workflows, or conditions where another tool like create_procedural_material or assign_material would be more appropriate. The intended use is only implied by the tool's name and short description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.