material.attach_image_texture

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

Annotations provide no meaningful hints (all false), so the description carries the behavioral burden. It discloses risk level, maturity, and prerequisites, but it never explains what changes occur in the material or scene, whether the operation replaces existing connections, or what side effects to expect.

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 compact and not bloated, with the requirements sentence adding some useful information. However, the first sentence duplicates the tool name/title and provides no real content, so the structure is adequate but not maximally effective.

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?

The tool has a nested object parameter, six total parameters, and a close sibling that needs differentiation, yet the description only supplies risk and access prerequisites. It lacks enough information for an agent to know what material/path values look like, what the operation does to the material, or how it differs from the similarly named sibling.

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 only 50%, and the two functional parameters 'material' and 'path' lack schema descriptions. The description hints that path refers to an approved asset-root image file, but it does not explain the structure of the nested path object or how 'material' should be referenced, leaving critical invocation details undocumented.

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 mostly restates the command identifier ('PartMe Blender Harness command `material.attach_image_texture`') without defining what the tool actually does. It mentions requirements and risk but no explicit verb+resource relationship, and it does not distinguish 'attach' from the close sibling 'blender_material_connect_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?

There is no guidance about when to use this tool instead of related material tools such as blender_material_connect_image_texture or blender_material_assign. The only context is a requirements statement, which covers prerequisites but not selection or comparison against alternatives.

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