animation.pose_keyframe

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

No behavioral traits are disclosed beyond the annotations, which are all false. 'Risk: standard' and 'maturity: L3' do not describe side effects, required scene state, or transaction behavior, so the agent remains blind to what invoking this tool changes.

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 short, but brevity is achieved by omitting substance rather than by tight, informative prose. A single sentence of metadata does not earn its place because it does not help select or call the tool.

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 9-parameter command with nested objects and no behavioral annotations, the description is radically incomplete. It lacks purpose, parameter semantics, prerequisites, and any indication of side effects, so an agent cannot safely invoke it.

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 only 44% schema description coverage and no parameter explanation in the description, key parameters like armature, bone, dataPath, and frame are left effectively undocumented. The description does nothing to compensate for the schema gap.

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 only restates the command name (`animation.pose_keyframe`) and adds risk/maturity metadata; it never states what the tool does, making it effectively a tautology rather than a functional definition.

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 given on when to use this tool versus alternatives such as blender_animation_insert_keyframe or blender_animation_shape_key_keyframe. The mention of session policy is an operational constraint, not a usage guideline.

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