blender_material_preview_render

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

No annotations are provided, so the description carries the full disclosure burden, and it covers the key trait: the operation happens in a 'temporary scene,' signaling a non-destructive, contained workflow. It also discloses the return contract ('returns the output path'). It does not explicitly confirm temp-scene cleanup, error behavior for nonexistent materials, or the time cost of Cycles, but the core safety-relevant behavior is well conveyed.

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?

Two sentences with zero waste: the first states the purpose, the second enumerates the pipeline in order. Every clause earns its place, and the distinctive behavior (temporary scene) is front-loaded rather than buried.

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?

With no annotations and no output schema, the description compensates by spelling out the full pipeline and the return value, which is the only source of return-type information. It differentiates from the large sibling set via the temporary-scene framing, and parameter usage is fully covered by the 100%-documented schema. Minor gaps remain—no explicit statement that the current scene is left untouched and no error-handling note—but nothing essential for correct invocation is missing.

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 coverage is 100%, so the schema already documents all five parameters with defaults and enums, making 3 the baseline. The description adds light contextual meaning by mapping 'chosen shape' to preview_shape and 'output path' to the return value, but it contributes no syntax, constraints, or formats beyond what the schema provides.

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?

States a specific verb ('Render') followed by a concrete workflow: creates a temporary scene, assigns the material, renders it, and returns the output path. The 'standard shape' scoping makes it clearly distinguishable from scene-level render siblings like blender_render_image.

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 establishes clear usage context: this is for isolated material previews on a standard shape in a throwaway scene, which implicitly separates it from blender_render_image (renders the actual scene) and blender_material_assign (assigns a material in a scene). It never names an alternative or states explicit when-not-to-use conditions, so the agent infers the boundary rather than being told.

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