set_pose_batch

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

With no annotations, the description carries the full burden. It usefully discloses that edits are 'local' (bone-local space) and that the entire batch is grouped into one undo step, which is meaningful behavioral context. It does not mention error handling or exactly what happens on invalid input, but the key mutation and undo semantics are present.

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 sentence with no filler. It front-loads the action and resource, then adds the key atomicity detail. Every word contributes to the tool's purpose.

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?

The tool involves a nested BoneChange object with a mode enum, so more semantic context would help. The description gives the core purpose and undo behavior, and an output schema exists, but it omits the absolute/delta distinction and does not guide the agent on when to choose this over set_bone_pose. It is adequate but has clear gaps.

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 needs to compensate for parameter meaning. While 'local Pose Bone edits' hints at the coordinate space, it does not explain the 'changes' array structure, the 'absolute' vs 'delta' modes, or how 'rotation_degrees' is applied. The schema's names and enums help, but the description adds little semantic value beyond what the schema already shows.

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?

Description states a specific action ('Apply'), a specific resource ('multiple local Pose Bone edits'), and a distinguishing behavior ('as one Blender undo step'). This clearly separates it from siblings like set_bone_pose, which implies a single-bone operation, and reset_pose, which clears poses rather than applying edits.

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?

The word 'multiple' implies the batch tool is for applying several pose edits at once, but the description never explicitly says to prefer set_bone_pose for single edits or mentions any alternatives. Usage context is implied rather than stated, and no when-not-to-use guidance is provided.

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