blender_materials

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

No annotations are provided, so the description carries full burden for behavioral traits. It does not disclose side effects, requirements (e.g., active object), permissions, or what happens if parameters are incompatible. The operation list implies creation/assignment but gives no details on state changes or error conditions.

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 well-structured, starting with a clear purpose then listing operations in a bullet-style. It is concise with no redundant sentences. Each sentence adds value, though the parameter descriptions in schema are separate. Slightly verbose but still efficient.

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?

Given the tool's complexity (23 parameters, 7 operations), the description is incomplete. It does not map operations to relevant parameters, advise on which parameters to set for each operation, or explain the output. An output schema exists but is not summarized. The agent lacks sufficient context for correct invocation.

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 baseline is 3. The description adds a high-level operation list but does not explain parameter semantics beyond what the schema already provides. For instance, it doesn't clarify which parameters are relevant for each operation, relying on parameter names and enums.

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 explicitly states the tool's purpose: 'Create and manage PBR materials in Blender.' It lists specific operations (e.g., create_fabric, create_metal) which clearly define the resource and actions. This differentiates it from sibling tools like blender_materials_baking (baking) and blender_shaders (shader editing).

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 does not provide any guidance on when to use this tool versus alternatives such as blender_materials_baking or blender_shaders. It lacks explicit 'when-to-use', 'when-not-to-use', or references to other tools. The agent must infer context from the operation list alone.

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