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 disclosing behavior. It does mention that the slot is created if it does not exist, but it does not state whether an existing material in that slot is overwritten, whether the object must exist, or any other side effects. For a mutation tool, this is insufficient behavioral transparency.

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 that front-loads the core purpose and includes the key behavioral detail about slot creation. There is no wasted wording, and it is appropriately sized for the tool's simplicity.

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?

The description is incomplete for a mutation tool without annotations or an output schema. It does not clarify behavior when the slot already has a material, whether the material must pre-exist, possible errors, or any return value. An agent cannot fully predict the tool's outcome from this description alone.

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 description must compensate. It adds semantics for the slot parameter (default 0, create if missing), which is beyond the schema's default null. However, it provides no additional meaning for object and material parameters, though their names are self-explanatory from the tool name and Blender context. The description partially compensates but does not fully clarify expected formats or values.

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 action: assign a material to an object's slot, with a default slot of 0 and creation of the slot if missing. This clearly distinguishes it from sibling tools like create_material (which creates materials) and batch_apply_material (which applies to multiple objects). The verb and resource are explicit.

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 no guidance on when to use this tool versus alternatives. It does not mention conditions like 'use this when the material already exists' or 'use batch_apply_material for multiple objects.' It only states what it does, not when to choose it over other material-related tools.

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