blender_procedural_material

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

With no annotations provided, the description must carry the behavioral burden. It does disclose the main behavior—creating a Principled BSDF material and binding it to an object—which is more informative than a bare 'creates material'. However, it does not mention important side effects such as whether existing materials are replaced, whether the object must already exist, or what happens if the material name already exists.

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 sentence with no filler, front-loading the key action and material type before listing the supported features. Every phrase adds useful information, and the structure is efficient for an agent to parse quickly.

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 full schema covers parameters well, so the agent can construct a valid call. However, the description lacks details about prerequisites (object must exist), the effect on existing material slots, and what the tool returns since there is no output schema. This leaves some gaps, but the core invocation path is understandable.

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 documents every parameter in detail (e.g., RGBA base_color, metallic factor, transmission weight). The description only summarizes 'metallic, roughness, glass transmission, or emission' at a high level, adding no new parameter-level meaning beyond the schema.

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 uses a specific verb ('Creates'), a clear resource ('physically-based (PBR Principled BSDF) material'), and an explicit binding action ('binds it to an object'). It also enumerates the supported material qualities, which distinguishes this tool from all sibling Blender tools, none of which handle materials.

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 clearly implies when to use this tool: when an object needs a PBR/Principled BSDF material with metallic, roughness, glass transmission, or emission characteristics. It does not explicitly name alternatives or exclusions, but the context is unambiguous given the sibling list, so an agent can infer this is the material-creation tool.

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