rig.clear_pose

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

No annotations exist, so the description must disclose behavioral traits. It indicates a write operation (clearing transforms) but does not mention whether it is reversible, if it requires specific permissions, or any side effects. The agent lacks cues about safety or destructiveness.

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, clear sentence that conveys the tool's action and scope without unnecessary words.

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 tool with one parameter and no output schema, the description adequately states the function but lacks context such as required mode (pose mode), whether it affects all bones including constraints, or what happens to the armature if it has no pose.

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?

The description does not mention the 'armature' parameter. Although the schema provides a title, the description adds no extra meaning. With 0% schema description coverage, the burden falls on the description, which is not met.

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 uses the verb 'clear' and specifies the resource 'pose bone transforms' with the outcome 'back to rest values'. This clearly distinguishes it from sibling tools like 'rig.set_pose_bone' which set individual bone transforms.

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 such as setting individual pose bones. There is no mention of prerequisites (e.g., the armature must be in pose mode) or exclusions.

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