blender_assign_material

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

Discloses the replacement behavior, which goes beyond the annotation flags. However, it doesn't clarify whether all material slots are replaced or just the active one, leaving some ambiguity.

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?

Single sentence, efficient, front-loaded with action and effect.

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 mutation tool, it lacks mention of error handling or prerequisites (e.g., material existence). The core action is clear, but it doesn't cover edge cases or return behavior. Adequate but incomplete.

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?

Only response_format has schema description; objects and material lack descriptions. The description implies their roles but doesn't specify identifier formats or required naming conventions. Given low schema coverage (33%), more compensation is expected.

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?

States a specific verb ('assign'), resource ('existing material to objects'), and the effect ('replacing their current slots'). It clearly distinguishes from material creation and listing siblings.

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?

Clear context: you assign an existing material. However, it doesn't explicitly mention alternatives like blender_create_material for new materials, nor any exclusions, so it lacks explicit when-not guidance.

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