set_pose_bone_transform

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

The idempotentHint annotation is not contradicted, and the description adds the 'pose space' context and location/rotation scope. However, it does not disclose behavior when both location and rotation are null, whether this replaces or adds to existing transforms, or if the object must be an armature in pose mode. The description adds some context but lacks deeper behavioral details.

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, front-loaded with the verb 'Set,' and contains no fluff. Every word contributes to defining the action and scope, making it as concise as possible.

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 is a simple setter with an output schema and idempotent annotation. The description covers the core purpose but omits important operational context such as whether the armature must be in pose mode, how the 'both null' case behaves, and any relationship to animation or keyframes. It is adequate for a basic setter but not fully complete.

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?

With schema description coverage at 0%, the description compensates by explaining that location and rotation are transform components in pose space. It implies the object and bone parameters from 'pose bone,' but does not specify the expected array formats (e.g., XYZ or quaternion), units, or null semantics. This provides basic meaning but not full clarity.

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 a specific verb 'Set' and clearly identifies the resource as 'a pose bone's transform,' specifying scope as 'location and/or rotation in pose space.' This distinguishes it from sibling tools like set_transform (object transform) and set_bone_property (bone properties).

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 phrase 'pose bone' and 'pose space' implies usage in pose mode for armature bones, but the description does not explicitly state when to use this tool versus set_transform or set_bone_property. No exclusions, prerequisites, or alternative references are provided; guidance is only implied.

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