animation.insert_keyframe

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

Annotations already indicate this is not read-only, not idempotent, not open-world, and not destructive. The description adds only generic 'Risk: standard; maturity: L3' and a reminder that session policy applies, which is process metadata rather than a disclosure of what the operation actually does to the Blender scene, the target object, or the animation data.

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 text is short, but it is under-specified rather than concise. It spends its sentences on boilerplate ('Risk: standard; maturity: L3') and a tautological command identifier instead of front-loading a meaningful statement of what the command does and its key constraints.

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 7 parameters, 4 required, and multiple closely related animation tools in the sibling list, this description is far too thin. It omits the command's purpose, how to specify the animation property, expected frame semantics, and any caveats about the session or transaction requirements, leaving an agent unable to invoke the tool correctly without external knowledge.

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 only 43%, covering only the _requestId, _authorization, and _transactionId metadata parameters. The core parameters dataPath, frame, object, and _expectedSceneRevision have no schema description, and the tool description adds no meaning for them. An agent cannot tell what dataPath should look like, how frame is interpreted, or what object references are valid.

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 tool name ('PartMe Blender Harness command `animation.insert_keyframe`') without stating what the tool does, such as which animation property it inserts or on what object. The title implies 'insert keyframe', but the description itself is a tautology of the name, not an explanation of behavior.

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 guidance about when to use this tool versus siblings such as blender_animation_pose_keyframe, blender_animation_shape_key_keyframe, or blender_animation_fcurve_edit. The description only says 'per-request argument checks and session policy still apply,' which is generic harness boilerplate and does not help an agent choose this tool over alternatives.

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