animation.shape_key_keyframe

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

No annotation contradiction exists: readOnlyHint, openWorldHint, idempotentHint, and destructiveHint are all false, and the description does not claim otherwise. However, the description adds only generic risk/maturity/session-policy metadata and no concrete behavioral detail such as whether an existing shape key is required, what scene mutations occur, or how the keyframe is applied.

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 this is under-specification, not effective conciseness. The sentence is mostly boilerplate and does not earn its place because it conveys no operational content about the tool's purpose, inputs, or effects.

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 nine parameters, four required ones, a broad sibling list of animation and shape-key tools, and no meaningful description, the definition is far from complete. Even though an output schema exists, the agent still lacks the basic information needed to decide when to call this tool and how to construct a correct request.

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?

The description provides no explanation of any parameter. Schema description coverage is only 44%, so the description needed to compensate, but it does not clarify frame, keyName, objectId, value beyond what the schema already says, or the transaction/revision fields. An agent is left to guess the meaning and relationship of the required 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 is essentially a tautology: it restates the command name 'animation.shape_key_keyframe' without any verb, resource, or outcome. An agent cannot tell from the description whether this creates, edits, removes, or queries a shape key keyframe, and it does not distinguish it from siblings like blender_animation_insert_keyframe or blender_animation_shape_key_add.

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 the many animation-related siblings. The only usage-related text is generic boilerplate about 'per-request argument checks and session policy', which says nothing about the conditions that should lead an agent to invoke this specific command.

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