set_pose_bone_transform

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

The only annotation is idempotentHint=true, so the description carries the burden of behavioral disclosure. It does not clarify whether omitting location or rotation preserves existing values or resets them, nor does it mention whether the armature must be in pose mode or whether this affects any pose data. The phrase 'pose space' adds some context but little beyond the name.

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 front-loaded sentence with no filler. Every word earns its place: the verb, target, and scope are all present, making it highly scannable for an agent.

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 simple setter with an output schema present and only idempotentHint as an annotation, the description is adequate but leaves important gaps: when to use it (pose mode? only with an armature object?) and the exact behavior when location or rotation is null. These omissions could lead to incorrect usage or unexpected side effects.

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 does clarify that location and rotation are the settable components and that they are alternatives ('and/or'), and 'pose space' gives coordinate context. However, it never describes the `object` and `bone` parameters, nor does it explain the expected numeric format (e.g., radians vs degrees, array length) for location and rotation.

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') with a precise resource ('pose bone's transform') and explicitly scopes the operation to 'location and/or rotation in pose space.' This differentiates it from siblings like set_transform (object transform) and set_bone_property (bone properties) via the phrase 'pose bone' and 'pose space.'

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 guidance about when to use this tool versus alternatives such as set_bone_property or set_transform. It does not mention prerequisites (e.g., pose mode, armature object), exclusions, or conditions that would help an agent select this tool over siblings.

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