blender_make_material

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

The description adds behavioral detail beyond the annotations by explaining what presets do concretely (car paint gets metallic plus clear coat, glass gets transmission and IOR 1.52, etc.) and how overrides/assignment work. Annotations already declare write/idempotency/safety hints, and the description is consistent with them.

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 three sentences with no filler: core action first, then concrete preset examples, then override and assignment behavior. Every sentence earns its place.

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 14-parameter creation tool with no output schema, the description covers the mode of operation, preset semantics, override mechanism, and assignment behavior, while the schema supplies parameter detail. It does not describe return values or name-collision behavior with existing materials, which keeps it just below a 5.

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 high at 93%, so the input schema already documents most parameters. The description adds a useful general rule ('Any socket can be overridden') and illustrative examples, but does not need to restate per-parameter details.

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 states a specific verb ('Create') and resource ('physically sensible PBR material') and clarifies the mechanism ('from a named preset'). This differentiates it from sibling tools like blender_create_material or blender_build_shader, which do not promise preset-driven PBR correctness.

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 clear context: use it when a named physical preset is desired, and mentions that any socket can be overridden and that `assign` handles object assignment in the same call. It does not explicitly name alternatives or exclusion criteria, so it stops short of a 5.

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