bone_setTransform

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

Without annotations, the description discloses two critical behaviors: it automatically creates keyframes and only changes supplied transform parameters (partial update). This goes beyond the schema's optional flags, although it doesn't address overwrite semantics or error handling.

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 three concise sentences without redundancy. It front-loads the purpose, then introduces keyframing and the partial-update behavior, making every sentence valuable.

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?

Considering the lack of annotations and output schema, the description covers purpose, keyframing, and partial updates, which is sufficient for core usage. Some gaps remain (e.g., overwriting existing keyframes, error conditions), but the schema documents all parameters completely, and the description compensates well.

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 coverage is 100%, so the baseline is 3. The description adds meaning by clarifying that all transform params are optional and that omitted ones remain unchanged—a partial-update semantic not fully explicit in the schema. This helps the agent avoid resetting unspecified parameters.

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 clearly states it sets the transform (angle, position, scale) of a bone at a specific frame and automatically creates keyframes. This distinguishes it from sibling tools like bone_selectBone (selection) and layer_setTransform (layer-level transform).

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 implies its usage via the formulation 'Set the transform of a bone at a specific frame' and the auto-keyframing note. It does not explicitly mention alternatives or when not to use, but the specificity of bone keyframing provides clear context among siblings.

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