wizard_batch_materials

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses a side effect ('Creates materials if they don't exist'), but it does not explain what happens to existing material assignments, whether the operation is atomic, or how failures are handled.

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 appropriately short, front-loaded with the core action, and includes a compact example plus an Args section. Every sentence adds value and there is negligible filler.

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 one-parameter tool with a simple input structure, the description covers the input format, optional fields, and a key side effect. It is nearly complete, though it would benefit from noting whether assignments replace or overwrite existing materials and what color values are valid.

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 coverage is 0% and the schema only describes an array of additionalProperties objects, so the description must compensate. It does by specifying the exact assignment keys ('object', 'material', optional 'color') and giving an example format. It lacks color ranges and object-name resolution details, but it adds essential meaning the schema omits.

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 clearly states a specific action ('Assign materials') and its batch scope ('to multiple objects in one call'), making it immediately distinguishable from the single-object assign_material sibling. It does not explicitly name an alternative tool, so it stops short of a 5.

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 batch phrasing implies when to use this tool—when multiple objects need material assignments at once—but it gives no explicit exclusions or comparison to alternatives like assign_material or batch_material_preset. The usage guidance is present but only implied.

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