remove_keyframe

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It identifies the destructive nature of the action but gives no details about exact-time matching, failure behavior when no keyframe exists, idempotency, or whether the operation is undoable. This is a significant gap for a mutation tool.

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, well-formed sentence that immediately conveys the core operation without unnecessary words. It is appropriately concise for a straightforward parameterized action.

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?

Despite complete parameter documentation, the tool has no annotations and no output schema, and it performs a destructive mutation. The description does not explain what happens after removal, how to verify success, what errors may occur, or any conditions required for the keyframe to exist. More behavioral context is needed.

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?

All four parameters are documented in the input schema with 100% coverage, so the schema already provides the necessary semantics. The description adds minimal value beyond restating the operation, so the baseline score of 3 is appropriate.

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 clearly states the action ('Removes'), the resource ('a keyframe'), and the scope ('from a clip component parameter at a specific time'). It is immediately distinguishable from sibling tools like add_keyframe, get_keyframes, and remove_keyframe_range.

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 implies this tool is for removing a single keyframe at a specified time, which gives some usage context. However, it does not explicitly state when to prefer this over remove_keyframe_range, or mention any prerequisite such as first retrieving keyframes with get_keyframes.

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