blender_material_set_color

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It only says 'set', implying mutation, but it does not disclose that the existing base color will be overwritten, whether the material must already exist, what happens if the material is not found, or whether the change affects all objects using that material.

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 a single clear sentence with no filler and the verb-object structure is front-loaded. It earns its place, though it is arguably too terse to carry the behavioral and usage context the tool needs.

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 mutating tool with no annotations and no output schema, the description is not complete. It lacks guidance on error behavior, overwrite semantics, and the distinction from material_set_principled, leaving an agent to guess important operational 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 description coverage is 100%, so the input schema already fully documents both material_name and color. The description adds no additional parameter detail beyond implying that the color parameter maps to the base color, so the baseline of 3 is appropriate.

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') and the resource ('base color of a material'), so an agent immediately knows what the tool does. It is specific enough to be distinguished from siblings like material_create or material_assign, but it does not explicitly differentiate itself from blender_material_set_principled, which may also affect base color among other settings.

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 gives no guidance about when to use this tool versus alternatives. It does not mention that this is for simple base-color changes only, nor does it point to material_set_principled for full material setups, leaving the agent to infer the correct scope.

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