pose_bone

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds the behavioral detail that transforms are relative by default, which is useful, but does not disclose side effects like overwriting existing pose transforms or any prerequisites. This matches the pattern of adding some context beyond annotations.

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 main action, and contains no fluff. It is appropriately sized for the straightforward action it describes.

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 6 parameters, a destructive operation, and an output schema not described, the description is too sparse. It omits prerequisites (e.g., armature/bone existence, Pose Mode), error conditions, the meaning of 'relative', and side effects. The brevity is not sufficient for a tool with this complexity.

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% (6 parameters, none described in the schema). The tool description only mentions the 'relative' default, adding a small semantic detail for that one parameter. However, it does not explain location, rotation, scale, bone_name, or armature_name, nor their formats or units, failing to compensate for the schema's lack of descriptions.

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 'Atur transform pose bone (relatif secara default)' clearly states the action (set/adjust), the resource (pose bone transform), and a key behavioral note (relative by default). This distinguishes it from sibling tools like reset_pose or add_bone.

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 description provides no explicit guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It only implies use for setting pose transforms without explaining context such as needing Pose Mode or how it differs from transform_object.

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