material.connect_image_texture

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

The description adds only 'Risk: standard; maturity: L3' and a request-requirements note, neither of which explains the tool's behavior: whether it creates a node, replaces an existing connection, requires a material with specific nodes, or how the image path is handled. Annotations are all false and don't provide a safety profile, so the description carries the burden and mostly misses it.

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?

It is short and easy to parse, but the first sentence merely repeats the tool name and the second is boilerplate. This is under-specification rather than earned conciseness; no useful content is front-loaded.

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 seven-parameter material command with a closely named sibling (blender_material_attach_image_texture), the description is far too thin. It omits prerequisites, connection semantics, path expectations, and the distinction from the attach tool; the output schema cannot make up for these missing input and effect details.

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?

The description provides no meaning for material, path, or usage; only the schema's enum and internal-ID field descriptions offer any help. With schema_description_coverage at 43% and core parameters undefined, the description does nothing to compensate.

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 restates the command identity ('PartMe Blender Harness command material.connect_image_texture') and then gives risk/maturity metadata, but never states that it connects an image texture to a material or what the resource and outcome are. The operation must be inferred from the tool name, making this closer to a tautology than a purpose statement.

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 or when to prefer a sibling such as blender_material_attach_image_texture. The note that 'Per-request argument checks and session policy still apply' is a generic harness requirement, not usage direction.

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