set_material_blend_mode

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

With no annotations, the description carries the burden. It states the operation and return type (confirmation dict). However, it does not disclose potential side effects, error conditions (e.g., material not found), or whether the change is reversible. For a simple setter, this is acceptable but could be improved.

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 extremely concise: three sentences covering purpose, parameters, and return type. No unnecessary words, and the structure is logical (purpose first, then details). Every sentence earns its place.

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 the presence of an output schema, the description is mostly complete. However, it lacks usage guidance (when to use vs. set_material_property) and does not mention prerequisites or error cases. It adequately covers the core functionality but misses some contextual details.

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%, so parameters have no schema descriptions. The description adds meaningful value by defining material_name as 'Name of the material' and listing the valid blend modes (OPAQUE, CLIP, HASHED, BLEND) for 'mode'. This compensates well for the lack of schema descriptions.

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 ('Set the blend mode of a material') and specifies the context (EEVEE render engine). This verb+resource+scope combination is specific and distinguishes it from sibling tools like assign_material or set_material_color.

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 when-to-use or when-not-to-use guidance is provided. The description mentions EEVEE, implying it's only for that engine, but does not clarify alternatives or prerequisites (e.g., material must exist). This is adequate but lacks explicit differentiation from set_material_property.

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