blender_manage_material

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

No annotations are provided, so the description carries the full behavioral burden. It implies mutation and includes a 'remove' action, but never states that removal is destructive, whether it is reversible, what happens to an existing material when reassigned, or any permission/idempotency characteristics. For a write tool with zero annotation coverage this is a meaningful gap.

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 compact, front-loaded with the purpose, and then enumerated per parameter with no filler sentences. The terse parameter list is efficient, though the action values are stated twice (once in prose, once in the action line), which is minor redundancy.

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 explained. However, with 8 parameters at 0% schema coverage, the description leaves object_name and material_name undocumented and gives no semantics for the 'remove' action, so an agent cannot fully predict behavior for all modes.

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, and it does for six of eight parameters: action values, color as RGBA/RGB float list, the 0.0-1.0 bounds for color/roughness/metallic, and emission as an RGB list with emission_strength as a multiplier. It omits object_name and material_name semantics, keeping it short of a 5.

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 first sentence names a specific verb set (creates, assigns, configures) and a specific resource (a Principled BSDF material on an object), so the tool's purpose is immediately clear. It does not distinguish itself from siblings like blender_modify_object or blender_manage_modifiers, but the resource is narrow enough to be unambiguous.

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 lists the valid action values ('assign', 'create', 'remove') but never explains when to pick each one or what state each requires (e.g., must a material already exist for 'assign' vs 'create'?). There is no guidance on when to use this tool instead of blender_modify_object or blender_create_object.

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