blender_normalize_character

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

With no annotations, the description carries the full burden, but it only says 'normalize,' which implies modification without explaining whether it is destructive, requires an armature, or how dry-run works. No additional behavioral context is disclosed.

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, efficient sentence that conveys the core purpose without wasted words. However, it could be slightly longer to include crucial behavioral or parameter context without losing conciseness.

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?

With six parameters, no annotations, and no output schema, the description is clearly insufficient. It fails to explain the normalization process, the role of dry_run, armature selection, or what happens after execution, leaving major gaps for an agent to use 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 compensate. It mentions height, horizontal center, and ground placement, which loosely map to target_height_m, center_xy, and place_on_ground, but ignores dry_run, armature_name, and create_checkpoint entirely. The mapping is implicit and incomplete.

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 it normalizes a character's height, horizontal center, and ground placement, which distinguishes it from sibling tools like validate or export. However, the verb 'plan' is somewhat ambiguous and not as direct as a single action verb.

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 provided on when to use this tool versus alternatives like blender_validate_character or blender_create_humanoid_character. The description does not mention prerequisites, context, or exclusions.

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