blender_bake_texture

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

It discloses that the operation writes image files to disk and that on failure the result says so and why instead of raising an exception. Since annotations only cover read-only/destructive hints, this added failure-behavior detail is valuable and goes beyond what the structured data provides.

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 carry the full message with no filler: purpose, prerequisites, engine recommendation, and failure behavior. The most important information is front-loaded.

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 covers prerequisites, engine choice, output, and failure behavior, which is sufficient for a moderately complex tool. Minor gaps remain around output_dir default behavior and file naming, but the core information an agent needs to select and invoke the tool correctly is present.

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 description adds no parameter-level meaning beyond what the schema already provides. With schema description coverage at 80%, the baseline is 3; the description does not clarify ambiguous parameters such as 'size' or the behavior of an empty output_dir.

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 opens with a specific verb and resource: 'Bake a material's procedural node setup down to image files on disk.' This clearly distinguishes the tool from siblings like blender_render or blender_generate_texture by identifying both the input (procedural node setup) and the output (image files on disk).

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 states clear prerequisites ('Needs UVs and a node-based material') and recommends Cycles as the reliable engine, giving the agent useful context for when this tool is appropriate. It does not explicitly name alternatives or state when not to use it, 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.