capcut_add_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 confirms that a keyframe is added but does not disclose whether existing keyframes are overwritten, whether the operation is reversible, whether it requires a specific app state, or what happens after invocation.

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?

One sentence with no filler. The core action, resource, and relevant properties are front-loaded, making the description easy to parse quickly.

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 mutation tool with no annotations and no output schema, this description is too thin. It does not explain how to construct a complete animation, whether repeated keyframes are supported, what valid value ranges are, or what the tool returns or changes. An agent would need to inspect the schema and guess at behavioral conventions.

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 coverage is 100%, so the schema already documents all parameters and their meanings. The description adds mild semantic grouping, mapping opacity to alpha and translation to x/y, but it does not provide meaningful extra meaning beyond the schema.

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 ('Adds'), a specific resource ('animation keyframe'), and enumerates the animatable properties (scale, rotation, translation, opacity). It is clear enough to distinguish from sibling tools like capcut_set_clip_transform, though it does not explicitly name any alternative.

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?

No guidance is provided about when to use this tool versus alternatives such as capcut_set_clip_transform or capcut_trim_clip. The description does not explain whether keyframes are needed for animation timelines, how multiple keyframes interact, or when a direct transform would be more appropriate.

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