reassign_material_slot

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

The description discloses that the operation affects all faces and moves them between material slots. However, with no annotations provided, it does not mention what happens to the source slot after reassignment, whether the destination slot must already exist, or how invalid indices are handled. That leaves some behavioral ambiguity for a mutating operation.

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 and front-loaded with a one-sentence summary followed by the use-case and Args list. The Args entries are useful and the text avoids verbosity. It could be slightly more structured, but it earns its place.

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 straightforward reassignment, the core inputs and purpose are covered. But without annotations or an output schema, the description omits edge-case guidance such as whether the destination material slot must exist, what happens if from_slot and to_slot are identical, and whether the source slot is preserved or removed. This is adequate but not fully complete.

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%, so the Args block carries the parameter documentation burden. It provides plain-language roles for all three parameters: target mesh object, source slot index, and destination slot index. It does not add indexing details or bounds, but it compensates for the missing schema descriptions.

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 uses a specific verb ('reassign') with a clear resource ('material slots'), and states the scope ('all faces'). This is clearly distinct from sibling tools like assign_material or delete_material, and the target mesh object is explicitly part of the operation.

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 a direct use case: 'Useful for replacing one material with another across the entire mesh.' This tells an agent when to reach for this tool. It does not explicitly name alternatives or state when not to use it, but the context is clear enough for a 4.

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