set_material_instance_static_component_mask

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

Annotations already declare readOnly false, destructive true, idempotent true, and openWorld false, so the safety profile is covered. The description adds useful behavioral context by noting that it rebuilds the static permutation, persists the change, and reads back via GetParameterValue.

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 front-loaded and concise, with no filler. The appended return shape is justified because no output schema exists, though it makes the definition slightly longer than a typical minimal entry.

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?

Given a mutation tool with rich annotations and full schema coverage, the description is nearly complete: it covers behavior, persistence, readback, Editor-only scope, and return shape. It does not describe failure modes such as a missing parameter or failed compilation.

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 100%, so all eight parameters including r/g/b/a and association are already documented in structured form. The description restates the R/G/B/A bool nature but does not add syntax or semantics beyond 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 states a specific verb and resource: setting a static component-mask (R/G/B/A bools) parameter override on a Material Instance Constant developing from a clear sibling getter and the static-switch variant. It is distinguishable from generic parameter override 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 description establishes clear context (static component-mask parameter override, Editor-only) but does not explicitly compare against alternatives such as set_material_instance_static_switch or set_material_instance_param_override. No when-not guidance is provided.

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