material_set_cutout

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

Annotations establish that this is a non-destructive, non-read-only mutation. The description adds useful behavioral detail beyond annotations: it sets the transparency slot to Cutout, disables Use Albedo Alpha, assigns the channel and Alpha Map, and re-reads from disk. It stops short of explaining broader side effects or whether existing material settings are preserved.

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 a single dense sentence with little wasted text, and it front-loads the core purpose before listing the configured settings. The telegraphic phrasing is efficient, though some clauses like 're-read from disk' could be clearer.

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 and annotations cover safety, so the description need not explain return values. However, for a six-parameter mutation tool with 0% schema coverage, the description leaves important parameter semantics and usage alternatives underspecified.

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%, so the description must compensate for six undocumented parameters. It explains channel (0 = R), alpha_map as the mask, and use_albedo_alpha being off, but it omits name, srgb, and especially threshold, which are important for correct invocation.

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 names a specific operation: configuring alpha-tested transparency from a mask image, including switching the transparency slot to Cutout and assigning the mask as Alpha Map. It is clearer than a mere restatement of the name, though it does not explicitly contrast itself with sibling material_set_texture or material_set_field tools.

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 phrase 'Alpha-tested transparency from a mask image' implies the intended use case, but there is no explicit guidance on when to choose this tool over material_set_texture, material_set_field, or other material tools. No prerequisites or exclusions are stated.

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