capcut_apply_transition

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

With no annotations provided, the description carries the behavioral burden; it does disclose the essential placement behavior and that it targets the following clip. However, it does not mention side effects such as replacing an existing transition, whether the draft is only modified in memory, or any pruning or validation behavior.

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?

Single sentence, efficiently front-loaded with the action and target, with a clarifying parenthetical. No wasted words.

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?

Adequate for a simple one-operation tool, but with no annotation or output schema it leaves gaps around valid transition sources, behavior on the last segment, and what the operation returns or commits.

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 80%, so most parameters already carry their own descriptions. The tool description adds only a little contextual framing around segmentId and transition, but no detail about the draft parameter or accepted value formats 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 uses a specific verb and resource ('Apply a transition') and precisely locates the operation ('after the selected clip segment (transitioning into the following clip)'). This clearly distinguishes it from sibling tools like capcut_apply_effect or capcut_apply_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 placement detail implies the tool is used when a transition between two adjacent clips is wanted, but it never states when not to use it or cross-references capcut_list_transitions for valid transition names. No alternative or exclusion is mentioned.

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