mat_set_slot

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this is a mutating/destructive operation. The description adds the editor-slot context but does not explicitly warn that an existing material in the slot will be overwritten. This is acceptable but does not go beyond what the destructive annotation already implies.

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 compact, front-loaded with the action, and provides a concrete motivation in two short sentences. The bilingual duplication is purposeful and does not add clutter. Every sentence contributes useful information.

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 two-parameter tool with clear annotations, the description is complete enough: it names the action, the slot range, and the typical scenario. No output schema is needed for such a straightforward mutation, and the destructive nature is already covered by annotations.

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%, with both slot and material parameters already documented. The description adds no parameter-specific detail beyond the schema, so it receives the baseline score appropriate when structured definitions carry the parameter meaning.

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: 'Put a material into a Material Editor slot (1..24)'. It also clarifies the unique purpose among many material tools by mentioning it is handy for surfacing a freshly created material in the editor, clearly distinguishing it from tools like mat_assign or mat_set_property.

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 gives clear context: use this to place a material into a specific editor slot, especially after creating a new material. It does not explicitly name alternatives such as mat_assign for object-level assignment, so it lacks explicit exclusion guidance, but the intended use case is stated directly.

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