production.texture_validate_channels

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

Annotations declare readOnlyHint=true, yet the description states 'apply=true writes only owned candidate materials'. A tool that can write is not read-only, so the description directly contradicts the structured safety metadata. The useful detail it does add (original slots, images, UVs, geometry and animation remain unchanged) cannot offset an agent being told the opposite of the annotation about whether this call mutates state.

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 poorly structured: the middle sentence is a run-on noun list ('material plan references ... technical QA, controlled lighting and a real visual review') that conveys no actionable structure. The genuinely important clause (the apply flag writes) is buried mid-sentence rather than 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?

With 7 undocumented parameters, an output schema that the description never references, and the safety profile undercut by a contradicting write flag, an agent still lacks the information needed to call this correctly. The non-mutation guarantees it does state are helpful but cover only part of the picture.

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 0% across 7 parameters, so the description carries the full burden and fails. Only 'apply' is explained; options, profile, material, definition, object_name and material_name get no semantics at all, and vague phrases like 'explicit channels/profiles' and 'material plan references' do not map reliably onto any of them.

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 name and first clause establish that this is a texture-channel validation tool that inspects/proposes by default and writes only when apply=true. But it never states what a 'channel' is validated against (naming, packing, colorspace, presence) and does not distinguish it from the many adjacent validators in the sibling list (material_validate_uv, texture_validate_colorspace, material_validate_profile). The purpose is recognisable but not sharp enough to pick it confidently among near-duplicates.

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 real, implied guidance in the mode toggle: inspect/propose first, then apply=true to write only owned candidate materials. However, no sibling alternative is named and no explicit when-not condition is given. The trailing clause about 'material plan references for lifecycle calls' and 'a real visual review before acceptance' reads as a workflow reminder rather than a selection rule.

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