blender_iso_bake_assets

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It lists outputs but does not disclose side effects, whether it writes or overwrites files, whether it requires an existing Blender scene, or whether the operation is destructive.

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 compact sentence that front-loads the verb and direct object with no filler. The dense jargon ('2:1 dimetric', 'mathematical collision diamonds') slightly reduces scannability but 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 4-parameter tool with no annotations and no output schema, this description is under-specified. It does not explain what archetypes are valid for, what the manifest contains, how tileWidth affects output, or what an agent should expect after 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 0%, yet the description mentions none of the four parameters by name. The schema names like tileWidth, archetypes, outputDirectory, and manifestFileName are somewhat self-explanatory, but the description adds no meaning about how they influence the bake or what values are expected.

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 operation ('Bakes') and the specific outputs ('asset definitions, mathematical collision diamonds, and engine manifests'). It distinguishes this from the sibling tool blender_iso_bake_2d_passes by focusing on asset definitions and manifests rather than 2D passes. It is slightly jargon-heavy and doesn't clarify what 'bakes' means in terms of outputs or files, so it stops short of a 5.

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?

There is no explicit guidance on when to use this tool versus siblings such as blender_iso_create_tile, blender_iso_build_room, or blender_iso_bake_2d_passes. The description implies asset-pipeline usage but does not state conditions, prerequisites, or exclusions.

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