blender_material_assign

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It communicates that the tool mutates an object's material assignment, but it does not disclose whether existing material slots are replaced, whether a new slot is created, what happens if the material or object does not exist, or any other side effects.

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 short sentence with no filler and the action is front-loaded. However, it mostly restates the tool name and offers no additional useful structure, so it is concise but minimally informative.

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 mutation tool with no annotations, no output schema, and three parameters, this description is incomplete. It omits prerequisites such as the material and object already existing, does not explain slot behavior, and gives no sense of error cases or return values, leaving an agent to guess important call details.

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 100% description coverage, so the baseline is 3. The description adds no additional meaning beyond 'material' and 'object'; it does not clarify the optional slot_index behavior or indicate whether material_name must reference an existing material.

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 core operation clearly: 'assign' a 'material' to an 'object'. It is specific enough to indicate the action, but it does not mention that the material must already exist or explain the role of material slots, so it does not fully distinguish itself from the many related material and object tools.

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 usage context or alternative selection guidance is provided. With sibling tools like blender_material_create, blender_material_set_principled, and blender_material_add_texture, the agent is left to infer when material assignment is the right operation versus material creation or material property editing.

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