Blender Set Material

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

No annotations provided. The description indicates mutation (assign/create) but does not disclose side effects like overwriting existing materials, error conditions, or required permissions. It lacks behavioral context beyond the basic action.

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, front-loaded with key information, no wasted words. Highly concise.

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 is adequate for a simple tool with well-documented parameters. However, it lacks explanation of return behavior or side effects, and does not compensate for the missing output schema. Could be slightly more informative.

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 100%, so the baseline is 3. The description mentions 'base color and metallic/roughness' which aligns with schema but does not add significant new meaning beyond the parameter 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 verb (assign or create), resource (material on Blender object), and key properties (base color, metallic, roughness). It distinguishes from sibling tools which deal with constraints, forces, transforms, etc.

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 on when to use this tool vs alternatives. It does not clarify when to assign vs create, or the prerequisites (e.g., object must exist). Siblings do not include other material tools, but explicit usage context is missing.

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