Delete a keyframe

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a deletion but does not state whether the change is reversible, whether undo is available, what permissions are needed, or what side effects occur on the owning animation or channel.

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 a single front-loaded sentence with no filler. It communicates the action and the two target-selection modes efficiently.

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 five-parameter deletion tool with no annotations and no output schema, the description is under-specified. It leaves out the animation parameter, safety/reversibility details, and the interaction between uuid and time, which an agent needs to invoke it correctly.

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 0% across five parameters. The description mentions uuid, time, bone, and channel, but it omits the animation parameter entirely and does not explain channel default behavior, uuid/time precedence, or expected formats.

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 states a specific verb and resource: delete a keyframe. It also distinguishes two identification modes, by uuid or by nearest time on a bone/channel, which cleanly separates it from siblings like bb_add_keyframe and bb_delete_animation.

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 explains two ways to identify the target keyframe, but it does not state when to use this tool versus alternatives such as bb_delete_animation, nor does it provide prerequisites or exclusions. Usage is only implied by the operation itself.

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