blender_create_humanoid_character

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

With no annotations, the description must disclose side effects, but it only says 'plan or generate,' leaving unclear whether it modifies the Blender scene, creates files, or respects dry-run semantics. No mention of checkpoints, file writes, or other behavioral traits.

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, focused sentence with no filler. Every word contributes to the core purpose, making it highly concise and easy to parse.

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?

Despite the tool's complexity (6 parameters, no output schema, no annotations), the description provides minimal context. It omits return values, side effects, relationship to sibling tools, and the meaning of 'plan' vs 'generate,' leaving the agent under-informed.

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 33%, and the description fails to explain parameters like height_m, archetype, dry_run, or create_checkpoint. The mention of 'seven canonical game actions' hints at output but does not clarify parameter meanings.

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 tool's function with a specific verb ('plan or generate') and resource ('original rigged humanoid'), and adds specificity with 'seven canonical game actions.' This distinguishes it from sibling tools like import, validate, and export.

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 implied: this is for creating a new humanoid character, contrasted with siblings for importing, validating, exporting. However, there is no explicit 'when to use' or 'when not to use' guidance, nor mention of alternatives.

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