set_material_slot

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

No annotations are provided, so the description carries the full behavioral burden. It only says 'set', implying mutation, but does not disclose side effects (e.g., overwriting existing slot assignments), error behavior for invalid slots or missing materials, or whether material names must reference existing materials. It lacks the context needed to safely predict the operation's impact.

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 a single, concise sentence with no filler words. It is front-loaded with the core action and resource. While extremely brief, it wastes no words and is easy to parse.

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?

Given that the tool has three required parameters and no annotation support, the description is insufficient. It doesn't explain parameter semantics, prerequisite conditions, or error handling. While an output schema exists, it cannot clarify input behavior. For a tool that mutates object state, more context is needed for an agent to invoke it correctly without trial and error.

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?

The input schema has zero descriptions for all three parameters (coverage 0%), and the description adds only generic references to 'object', 'slot', and 'material' without explaining their formats, ranges, or constraints. For example, slot_index could be zero-based or one-based, and material_name might need to be an existing material or be created on the fly. The description does not compensate for the schema gap.

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 the action ('set'), the resource ('a specific material slot on an object'), and the target ('to a given material'). It is clear and specific, and the mention of 'specific' hints at slot-index-based assignment, distinguishing it from the broader assign_material sibling. However, it does not explicitly name alternative tools or contrast with them.

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 on when to use this tool versus alternatives like assign_material or apply_material_to_all. There is no mention of conditions, prerequisites (e.g., object must exist, slot must be valid), or hints about slot indexing conventions. The agent must infer usage from the name and description alone.

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