blender_materials

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

The description says 'create and manage' which implies modifications to the Blender scene, but it does not disclose side effects, required permissions, reversibility, or what gets destroyed/changed. Annotations provide no safety hints (all false), leaving the description to carry the burden, and it does not.

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 concise and well-structured: a one-sentence summary followed by a bulleted list of operations. Every line adds information, and the format 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?

The description provides a solid high-level overview but misses critical operational context: it does not indicate which parameters apply to each operation (e.g., which parameters are used for create_metal vs create_fabric). An output schema exists to cover return values, but the description still leaves uncertainty about parameter usage per operation.

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?

The input schema already covers parameter descriptions at 100%, so baseline is 3. The description adds value by explaining the operation parameter's enum values in plain language and grouping them by material type, which helps agents select the right operation. It does not map all parameters to operations, but the schema descriptions handle 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?

The description clearly states the tool's purpose as 'Create and manage PBR materials in Blender' and enumerates specific operation types (create_fabric, create_metal, etc.), making the scope explicit. It distinguishes itself from sibling tools like blender_textures or blender_shaders by focusing on PBR material creation and assignment.

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 provides clear context: it is for creating and managing PBR materials, with a list of sub-operations. However, it does not explicitly state when to use this tool over alternatives (e.g., blender_shaders or blender_textures) or provide exclusion criteria, so it falls 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.