gameforge_blender_ortho_turntable_bake

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

With no annotations, the description carries the full burden; it does disclose the produced artifacts and that execution requires Blender 4.x `bpy`. It omits key behavioral facts for a render/bake job: where files land, disk writes and overwrite behavior, runtime cost, and whether the tool is safe to re-run.

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?

A single dense sentence that front-loads the action and then enumerates outputs, with no filler sentences. It is jargon-heavy with backticked identifiers, but every clause carries information.

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?

No output schema and no annotations, so the description must stand alone; naming the emitted files compensates for the missing output schema. However, for a 7-parameter bake job it leaves frame-range semantics, AA toggle behavior, and return/status reporting entirely unexplained.

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 only 14%, so the description must compensate — it partially does by listing the six valid clip names (schema only says default 'walk') and explaining `execute_in_blender`. But `frame_start`, `frame_end`, `pixel_crisp_aa_off`, `project_id`, and `character_id` remain undefined anywhere, leaving most of the 7 parameters opaque.

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 and artifact — generate an 8/16-direction orthographic multi-pass baker — and enumerates the exact render passes produced (Beauty RGBA, depth, lineart, tangent normal, socket JSON). It is clearly distinct from rigging/export siblings, though it never explicitly names a sibling to route away from.

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 when-to-use guidance: nothing says whether this replaces or follows `gameforge_generate_turnaround_workflow`, `gameforge_blender_rig_and_sockets`, or `gameforge_synthesize_procedural_frames`. The parenthetical '(and optionally run in Blender 4.x)' hints at a dry-run mode but never states the condition for choosing it.

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