assign_material

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

No annotations are provided, so the description must carry the burden. It does not disclose important behavioral traits such as what happens if the material doesn't exist, if the slot index is out of range, if the operation is destructive (overwrites existing material), or any error conditions. The description only mentions the prerequisite that material must already exist.

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 one clear purpose sentence followed by a brief parameter list. It is front-loaded and contains no unnecessary information. Could be slightly more structured, but overall efficient.

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 simple assignment tool, the description lacks completeness. It does not mention return values, side effects, or prerequisites such as the object needing material slots. Given many sibling tools and no output schema, more context is needed to ensure correct usage, especially regarding when to use this versus other material-related tools.

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 description adds value beyond the schema titles by providing brief explanations: 'Target object', 'Material to assign (must already exist)', and 'Material slot index (default 0)'. However, it does not specify constraints like slot must be non-negative or that material_name must match an existing material exactly. Given 0% schema description coverage, the description partially compensates but is not detailed enough for a 4.

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 the action: assign an existing material to an object's material slot. It uses a specific verb and resource, and the purpose is distinguishable from siblings like create_material or set_object_material_color, though it does not explicitly name alternatives.

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. It mentions the material must already exist, but does not provide context such as 'Use after create_material' or 'For changing color, use set_object_material_color instead.' Lacks when-not-to-use or exclusions.

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