blender_pose_library_save

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

The description discloses a meaningful side effect: bone transforms are stored as custom properties on the armature. However, with no annotations provided, it does not cover important behavioral details like whether an existing pose with the same name is overwritten, whether pose mode is required, or what happens on failure.

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 concise and front-loaded: the first sentence states the core action, and the next two sentences add useful side-effect and filtering detail. No wasted words or redundant restatements of the tool name.

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 mutation tool with no annotations and no output schema, the description covers the core behavior and storage mechanism but leaves gaps around overwrite behavior, prerequisites, and error conditions. It is adequate for understanding the main action but not fully complete for reliable invocation.

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 schema already documents each parameter. The description adds a little context by indicating that the saved data includes location, rotation, and scale, and that bone_filter limits which bones are saved, but it does not substantially enrich the parameter meanings beyond what the schema states.

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 ('Save') with a clear resource ('current pose of an armature') and explains the outcome: a named pose stored as custom properties. This distinguishes it well from the sibling blender_pose_library_apply, which is about applying rather than saving.

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?

There is no explicit guidance on when to use this tool versus alternatives, such as blender_pose_library_apply or the animation/keyframe tools. The description implies a save operation but does not state context, prerequisites, or exclusions.

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