mat_set_emission

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

Annotations signal mutation (readOnlyHint=false) and destructive potential (destructiveHint=true), so the description is not required to repeat that. It adds useful context by disclosing exactly which material fields are modified for each material class and that the amount is also set. It does not contradict the annotations.

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 entry is compact, front-loads the core action, and provides bilingual coverage without redundant prose. Every sentence conveys either the operation, the affected properties, or the material-type mapping.

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 simple setter with destructive annotations and fully covered schema, this description is nearly complete: it explains material-type-specific property names and maps inputs to real material classes. It stops short of describing behavior on unsupported material types or naming alternatives, but that gap is minor given the schema and annotation context.

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 parameters already document color format, amount semantics, and material name. The description does not add significant parameter meaning beyond the schema; the baseline score of 3 is appropriate.

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 action on a specific resource: set material emission, with the exact affected properties depending on material type (PhysicalMaterial emission_color vs StandardMaterial selfIllumColor) and emission amount. This clearly differentiates it from sibling material setters like mat_set_diffuse, mat_set_specular, and mat_set_opacity.

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?

No guidance is provided about when to choose this tool over alternatives. It does not mention mat_set_property or other material-setting siblings, and gives no exclusions or conditional recommendations. The only implied usage comes from the tool name, which is insufficient for the large sibling set.

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