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 burden. It confirms this is a mutation of an existing material's color but omits whether the material must exist, whether it errors or creates one, and whether the change is undoable (a relevant concern given the sibling blender_history_undo).

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?

Two short sentences, front-loaded with the action and followed by the one piece of format detail that matters. Nothing is wasted and it is easy to scan.

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?

An output schema exists, so return values need not be described. However, for a two-parameter mutation tool with zero annotation support, the missing preconditions (does the material need to exist?) and the undefined 'name' parameter leave gaps an agent would have to discover by trial.

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 does this well for 'color' by specifying the accepted formats ([r,g,b] or [r,g,b,a]) and the 0-1 value range, but leaves 'name' completely unexplained — presumably a material name, but the agent must infer this.

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 (set) plus resource and property (base color of a material), which is immediately actionable. It implicitly distinguishes itself from siblings like blender_material_set_texture and blender_material_assign, though it never names or contrasts them explicitly.

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 when-to-use guidance, no alternatives mentioned, and no prerequisites stated. It does not say whether the material must already exist, whether 'name' refers to an existing material, or what happens if it does not.

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