blender_set_pose

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

With no annotations, the description carries the safety burden, and it does flag the critical destructive behavior: reset=True clears other bones first — and the schema default is true, so this is destructive by default. It doesn't cover error behavior for unknown bones or whether the write is undoable, so it is strong but not complete.

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?

Three tightly packed sentences, front-loaded with the core action and payload shape before the reset caveat and the follow-up tool. Every clause earns its place.

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 3-param mutation tool with no annotations, no output schema, and a nested object, the description covers the tricky parts (payload shape, destructive reset default, recovery via reset_pose). Missing only armature semantics and failure modes.

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 explains the nested rotations format and the reset flag semantics well, but says nothing about the required 'armature' string parameter, leaving one of three parameters undocumented.

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 (Set) and resource (local Euler rotations on pose bones), specifies units (degrees), and gives the exact payload shape (rotations={"bone": [x, y, z]}). It also names the sibling it complements (blender_reset_pose), so an agent can distinguish it from pose-related neighbors.

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?

Gives useful operating context: reset=True clears other bones first, and blender_reset_pose is named as the way back to rest. It stops short of routing the agent against other pose siblings like blender_pose_aim or blender_key_pose, so it is clear context without explicit exclusions.

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