assign_material

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the action 'assign.' It does not reveal whether an existing material in the slot is replaced, what happens with an invalid slot index, or whether the material must already exist in the scene.

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 core action, and organized cleanly into an Args list. No unnecessary prose is present, though the brevity contributes to the lack of behavioral detail.

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 3-parameter mutation tool with no output schema and no annotations, the description is too thin: it lacks failure behavior, side effects, prerequisites, and any note about whether the slot index is zero-based. An agent could call it with an existing material and destination slot, but it would not know what to expect when the material or slot is invalid.

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 schema has 0% description coverage, so the Args section needed to add real meaning. However, 'material_name: Material to assign' and 'slot: Material slot index' mostly restate the parameter names, while 'object_name: Target object' adds only minimal clarity. It also omits that slot is optional with a default of 0, which is already in the schema but not explained.

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 opening sentence, 'Assign a material to an object's material slot,' names a specific verb, resource, and target. It is clearly distinct from create/delete/set-material tools, though it does not differentiate itself from the similarly named sibling reassign_material_slot.

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 given about when to use this tool versus alternatives such as reassign_material_slot, set_material_property, or create_material. There is no mention of preconditions like the material needing to already exist, or exclusions for other workflows.

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