production.material_configure_emission

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds meaningful behavior beyond those annotations: inspect/propose is the default, apply=true writes only owned candidate materials, and original slots, images, UVs, geometry, and animation remain unchanged. This clearly scopes the write behavior and non-destructiveness.

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 and front-loads the default/apply distinction. However, the second sentence is a dense, vague list ('lifecycle calls, explicit channels/profiles, technical QA, controlled lighting and a real visual review') that reads as a run-on process requirement rather than focused guidance.

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, so return values need not be explained, and annotations cover the safety profile. But for an 8-parameter configuration tool with no schema descriptions, the description leaves most parameter meanings and selection behavior unaddressed. Additional context about what 'definition', 'options', or 'operation_id' control 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 8 parameters. The description explains 'apply' and hints at 'profile' via the phrase 'channels/profiles', but it does not explain material, material_name, definition, object_name, operation_id, or options. The remaining six parameters are undocumented in both the schema and the description.

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 the resource (emission configuration) and states the primary behavior: inspect or propose by default, write candidate materials when apply=true. It does not explicitly distinguish itself from sibling configure tools like material_configure_opacity or material_configure_sss, but the verb+resource is clear enough to identify the tool's role.

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?

It gives a useful default-vs-apply rule and mentions prerequisites such as material plan references, technical QA, controlled lighting, and visual review. However, it does not name any alternative sibling tool or state when another material tool would be more appropriate, which is a notable gap in a large material tool family.

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