assign_material

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

No annotations are provided, so the description carries the full burden. It says 'assign' but does not disclose whether this replaces the existing material, affects the active material slot, or requires specific object types. The outcome and side effects are unspecified.

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 single sentence is concise and front-loaded with the action, but it lacks any structure such as usage notes or caveats. It is appropriately short but offers no additional organized information.

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 has only two parameters and no annotations, the description is minimal but still leaves significant gaps: no mention of output, side effects, or preconditions. An agent calling this would likely need to guess whether it assigns by name to a specific object or works on the current selection. It is incomplete for reliable invocation.

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 description only repeats the parameter names implicitly. It adds no meaning about the expected format or semantics of object_name and material_name, such as whether they are names, paths, or IDs.

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 verb ('assign') and resource ('material to an object'), making the core purpose clear. However, it does not differentiate from sibling tools like set_material_slot or apply_material_to_all, which could also assign materials, so it misses an opportunity to disambiguate.

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 guidance is provided on when to use this tool versus alternatives such as set_material_slot or apply_material_to_all. An agent has no indication of selection criteria or context.

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