production.material_analyze_texture_sets

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

The annotations declare readOnlyHint=true, yet the description explicitly says "apply=true writes only owned candidate materials," which is a direct contradiction. The immutability statement ("Original slots, images, UVs, geometry and animation remain unchanged") is genuinely useful disclosure, but it does not resolve the write/read conflict an agent must reason about.

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 sentences, front-loaded with the tool name restated from the tool id (waste). The middle sentence is a run-on list of prerequisites that mixes QA workflow advice with parameter hints and is hard to parse into actionable instructions.

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 7-parameter tool with zero schema descriptions, the description leaves the majority of inputs and their interactions undocumented. An output schema exists so return values need not be explained, but the contract for selecting materials/definitions and profiles is missing.

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, yet it only explains `apply` (default false, writes candidates). The other six (options, profile, material, definition, object_name, material_name) are never defined, and "explicit channels/profiles" is the only oblique hint at `profile` semantics.

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 states the resource (texture sets for a material) and a dual mode ("inspect or propose by default"), but "inspect or propose" is vague about what is actually analyzed or produced. It never distinguishes this tool from nearby siblings such as material_analyze_pbr, material_analyze_nodes, or texture_inspect, so an agent cannot confidently pick it over those.

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 a usable default/mutation split ("inspect or propose by default; apply=true writes") plus workflow hints about plan references, channels/profiles, QA, lighting and visual review. However, none of this is framed as when-to-use-this-vs-a-sibling, and the guidance is a jargon-laden checklist rather than explicit selection criteria.

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