production.material_render_preview

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

Beyond the annotations, the description discloses that the default invocation only inspects/proposes while apply=true writes and is limited to 'owned candidate materials', and it explicitly guarantees original slots, images, UVs, geometry and animation remain unchanged. That is meaningful behavioral context (scope of effect, non-destructiveness) that the readOnlyHint=false / destructiveHint=false annotations alone do not convey.

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 most important fact (preview/propose by default, apply writes) is front-loaded, which is good. But the second sentence piles 'lifecycle calls, explicit channels/profiles, technical QA, controlled lighting and a real visual review' into a vague checklist that neither guides invocation nor earns its length.

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?

The presence of an output schema relieves the description of explaining return values, and the mutation semantics of apply are covered. However, given 8 undocumented parameters and a rendering/QA workflow that overlaps several siblings, the description leaves too much of the call contract to inference.

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 8 parameters, so the description carries the full burden, yet it only explains 'apply' and gestures vaguely at 'explicit channels/profiles'. material, definition, object_name, operation_id, material_name and options are entirely undefined in both places, which is a serious gap for an 8-param tool.

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 frames the tool as 'inspect or propose by default' with an 'apply=true' write mode, but never plainly states that it renders a material preview image, which is what the name implies. It does not distinguish it from close siblings like material_render_multilighting, qa_render_preview, or material_compare_before_after, so an agent cannot cleanly separate it from alternatives by purpose alone.

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 guidance ('Use material plan references for lifecycle calls, explicit channels/profiles, technical QA, controlled lighting and a real visual review before acceptance') is a workflow admonition rather than a when-to-use rule, and it never names an alternative tool or the condition that selects one. There is no explicit statement of when to use this vs. material_render_multilighting or qa_render_preview, leaving the choice ambiguous.

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