capcut_add_keyframe

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that the operation adds keyframes, but it does not state whether existing keyframes are preserved or replaced, what "smooth" means in implementation terms, or that the change is part of a draft that may require saving.

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, direct sentence with no filler and is front-loaded with the verb and target. Every word earns its place; the parenthetical property list is a useful compact summary.

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 mutating operation with four required parameters, no annotations, and no output schema, the description is too thin. It does not address existing keyframe behavior, value-range expectations, or the save/discard workflow implied by sibling tools, leaving an agent to infer important operational context.

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 schema already documents most parameters well, including the property enum and keyframe item fields such as timeOffsetSec and value. The description only adds a redundant property list and does not explain the undocumented draft parameter, so it falls at the baseline.

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 the specific verb "Add" with the resource "smooth animation keyframes to a segment" and lists the animatable properties, so the operation is immediately clear. It does not explicitly contrast with siblings such as apply_animation or set_props, though the keyframe terminology mostly differentiates it.

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 choose this tool over alternatives like capcut_apply_animation or capcut_set_props, and no exclusions or prerequisites are mentioned. The only implied use case is from the action itself: adding keyframes for animation.

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