blender_iso_bake_2d_passes

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

With no annotations, the description carries the full burden for behavioral disclosure, but it does not mention side effects such as writing image files, overwriting outputs, or requiring an existing object/material setup. It merely states the action and the list of passes.

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 tight sentence with no filler. The verb, resource, pass list, and scope are all front-loaded, and every word contributes to the meaning.

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 tool with five parameters, no output schema, and no annotations, this description is far too sparse. It omits prerequisites, file-output behavior, naming conventions, return values, and how the tool interacts with the Blender scene, so an agent cannot reliably invoke it correctly.

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 0%, so the description must explain objectName, baseName, tileWidth, and outputDirectory. It only repeats the pass names already present in the schema enum, adding no semantic value for the other four parameters.

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 names a specific verb ('Bakes'), a specific resource ('secondary 2D render passes'), and the scope ('for isometric sprites'), and it enumerates the exact passes: albedo, normal_2d, depth, shadow_mask. This is specific enough to distinguish it from the broader sibling blender_iso_bake_assets.

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 is given for when to use this tool versus alternatives such as blender_iso_bake_assets, nor are prerequisites or exclusions mentioned. The only usage signal is the implied context from the verb and resource.

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