assign_material

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

With no annotations, the description carries the full burden. It does disclose the key behavioral trait of replacing versus appending a slot, which is valuable. However, it omits other side effects, prerequisites (e.g., material must exist), or error conditions, leaving notable transparency gaps for a mutation tool.

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 two concise sentences, front-loaded with the primary action and immediately clarifying slot behavior. No wasted words or redundant restatements of the schema.

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 covers the core functionality and slot behavior, and an output schema exists so return values are handled. It lacks prerequisites (e.g., material/object must exist) and error scenarios, but for a simple assign tool it is reasonably complete.

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 effectively explains the 'slot' parameter's behavior (replace vs append). However, it does not add meaning for 'object' or 'material' beyond their obvious roles, and multi-line schema details are not addressed. Partial compensation.

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 a material to an object.' It also clarifies slot behavior (replace vs append), which distinguishes it from related material tools like create_material or set_material_property. This goes beyond the tool name and provides concrete scope.

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 implies usage for assigning materials to objects, but does not explicitly state when to prefer it over alternatives or mention any exclusions. The slot behavior gives some context, but it lacks direct sibling differentiation like 'use X instead of Y.'

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