material_assign

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

With no annotations, the description carries full burden. It states assignment but does not detail side effects (e.g., whether existing materials are replaced), error behavior if material or object doesn't exist, or undo impact. Only the slot_index arg gives a hint about appending vs replacing.

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 concise with a clear one-line purpose followed by a structured arg list. No unnecessary words. However, it could be slightly improved with a more natural prose intro.

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 the tool's simplicity and lack of output schema, the description covers the basic operation but lacks error handling details, confirmation of success, and does not mention whether the operation is undoable. Missing some context for a complete understanding.

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?

Despite 0% schema coverage, the description provides meaningful context for all three parameters: object_name, material_name (with precondition hint), and slot_index (with usage explanation). This adds value beyond the bare schema.

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?

Description clearly states 'Assign a material to an object' with specific verb and resource. It distinguishes from sibling 'batch_assign_material' by implication of single object, but does not explicitly differentiate, preventing a top score.

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 explicit guidance on when to use this tool versus alternatives like 'set_material' or 'batch_assign_material'. Prerequisites are only hinted at in the arg descriptions (material must exist). No when-not or alternative tools mentioned.

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