blender_material_create

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It does not state whether the new material becomes active, whether a duplicate name is replaced or creates another material, whether shader nodes are required, or what the tool returns upon success.

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 efficient sentence with no filler. However, it is so minimal that it misses behavioral context that could be added without becoming verbose.

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 mutation tool with no annotations and no output schema, the description is too thin. An agent cannot tell what side effects occur (e.g., assignment to active object, selection of the newly created material) or what a successful call returns, which matters when coordinating with the many sibling material tools.

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 schema already documents the name and use_nodes parameters. The description adds no parameter-level meaning beyond the schema, which keeps this at the baseline rather than higher.

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?

"Create a new material" states a clear verb and resource. It distinguishes itself from sibling material tools like set_color, assign, and list, though it doesn't explicitly name them or explain the exact scope of what 'create' entails.

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 guidance on when to use this tool versus alternatives such as blender_material_assign or blender_material_set_principled. There is no mention of prerequisites, whether the material is created as a standalone data-block, or whether it gets assigned to any object.

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