material_set_texture

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

Annotations already declare this is a non-readonly, non-destructive, closed-world mutation. The description adds real behavioral context beyond that: the field is cleared before writing so a changed file is re-read, `srgb`/`mipmaps` inherit the previous texture's settings, and an empty path clears the field. It does not cover failure modes (missing file, invalid slot) or what wrapping/filtering default to.

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?

Three tightly packed sentences: what it does first, then concrete slot/field examples, then the behavioral caveats. No filler, and the clear-then-re-read note is separate from the empty-path-clears note rather than redundant.

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?

An output schema exists, so return values need no explanation, and the mutation semantics are covered for the main path. The remaining shortfall is the unexplained `wrapping`/`filtering` options and no note on what happens when the path is invalid or the target material is absent.

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 0%, so the description must carry parameter meaning. It explains `slot` and `field` by example, `path` (empty clears), and the fallback semantics of `srgb` and `mipmaps`, but leaves `wrapping`, `filtering`, and `name` (the target material) completely unexplained — a third of the parameters remain opaque.

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?

States a specific verb and resource: putting an image file into a texture field, with concrete slot/field examples ('albedo'/'Albedo Map', 'surface'/'Normal Map'). It is distinguishable from generic siblings like material_set_field by being texture-specific, though it never explicitly says so.

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?

Gives implicit usage guidance via the empty-`path` clearing case and the slot/field examples, so an agent knows how to target a texture slot. However, it never says when to use this instead of material_set_field, material_set_cutout, or material_import, nor what preconditions (existing material, file on disk) are required.

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