material.connect_image_texture

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

Annotations already indicate readOnly=false, openWorld=false, idempotent=false, and destructive=false, so the description's added value is limited to 'Risk: standard; maturity: L3' and a generic requirements reminder. It does not disclose what side effects occur, whether the material's existing nodes are replaced, or what happens on failure.

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, but its first sentence is pure tautology and the second is generic operational boilerplate. It is not concise in the sense of packing useful information into few words; it simply omits the substance almost entirely.

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?

Despite having an output schema, the description is far too thin for a 7-parameter tool with a low schema coverage rate. It leaves the operation's purpose, parameter semantics, and behavioral effects unexplained, so an agent cannot reliably determine what to pass or what the invocation will do.

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 43%, and the core parameters material, path, and usage have no schema descriptions. The description does not explain what path should point to, what material identifier is expected, or how the usage enum values map to node sockets, leaving the agent without the semantic information needed to populate the required fields.

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 only repeats the tool's name and title as a command label ('PartMe Blender Harness command material.connect_image_texture') and adds risk/maturity boilerplate. It never states what the tool actually does, such as connecting an image texture node to a material or wiring a texture into a given usage slot.

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_attach_image_texture or blender_material_assign. The only usage-related content is a generic requirement note about argument checks and session policy, which does not help an agent select or invoke the tool.

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