material.attach_image_texture

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

Annotations are all false, giving no safety or side-effect hints. The description adds 'Risk: standard; maturity: L3' but does not disclose the tool's actions, such as whether existing textures are overwritten or how the material node graph changes. No contradiction, but no real behavioral transparency.

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 text is brief, but it front-loads the command name (a tautology) rather than a purpose statement. The requirement list is useful but does not compensate for the lack of substantive content.

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 mutation tool with required `material` and `path` parameters and no description of effects, the definition is incomplete. An agent cannot reliably determine what the tool does or what side effects to expect. The output schema does not compensate for the missing 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 descriptions cover only `_requestId`, `_authorization`, and `_transactionId`; `material` and `path` have no descriptions. The description mentions 'approved asset root' and 'existing image file' but does not explicitly tie these to `path` or explain the expected values or formats. Minimal added value over the schema.

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 repeats the command name (`material.attach_image_texture`) without explaining what the tool actually does. It does not distinguish from the similar sibling `material.connect_image_texture`, so an agent cannot tell them apart from the description alone.

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 lists requirements (approved asset root, existing image file) but provides no guidance on when to use this tool versus alternatives. It never mentions the sibling `material.connect_image_texture` or any other decision context.

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