gameforge_blender_rig_and_sockets

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

With no annotations, the description carries the full behavioral burden. It does disclose real side effects — metric height normalization (mutates the mesh), bone binding, optional retargeting, and six generated Actions — but says nothing about whether existing rigs are overwritten, where outputs are written, or what happens if Blender is unavailable. The Blender-execution optionality is at least surfaced.

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 content is relevant and front-loaded, but it is delivered as one dense run-on sentence packed with parentheticals, backticks, and an exclamation mark. Splitting the generation, retargeting, and animation-capability clauses would make it scannable.

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 complex, five-parameter, no-annotation, no-output-schema Blender pipeline tool, the description covers the what but not the operational contract: output artifacts, overwrite behavior, Blender availability requirements, and one wholly undocumented parameter remain unaddressed.

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 20% (just external_mixamo_fbx_path), so the description must compensate. It partially does — Mixamo/BVH retargeting, optional in-Blender execution, and height normalization map to three of the five parameters — but generate_mannequin_if_mesh_missing is never mentioned anywhere, leaving a genuine gap.

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 states a highly specific verb-and-resource pair: generate a 19-bone humanoid rig, paper-doll sockets, and a procedural animation builder using `bpy` in Blender 4.x. That specificity makes it easy to tell apart from siblings like gameforge_generate_3d_from_sheet or gameforge_blender_ortho_turntable_bake, though it never explicitly names those alternatives.

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?

Usage is only implied through phrases like 'so static 3D meshes animate immediately' and 'retargets external Mixamo/BVH .fbx clips if provided'. There is no explicit statement of when to pick this over the mesh-generation or turntable-bake siblings, nor any when-not guidance.

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