capcut_add_transition

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

No annotations are provided, so the description must carry behavioral disclosure. It only says 'Adds' and gives examples, without explaining side effects on existing transitions, whether the operation is reversible, or what the tool returns 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 front-loaded sentence with no filler. The example list is slightly redundant with the schema enum but still aids readability without bloating the description.

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 selecting the tool and invoking it with schema-documented parameters, but incomplete for edge cases: no annotations and no output schema mean the description should also note what the result is or what conditions are required for a valid transition between clips.

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 100%, so the schema already documents all parameters. The examples in the description overlap with the transition_name enum but do not add meaningful semantic detail beyond what the schema provides.

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?

States a specific verb ('Adds') and resource ('transition effect') with clear placement context ('between clips on a video track'). The examples clarify common variants and distinguish it from sibling editing tools such as add_video_clip, trim_clip, and add_text.

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 condition for using this tool is implied: you use it when you want a transition between clips on a video track. However, it does not explicitly state when not to use it, name alternatives, or mention prerequisites such as having two adjacent clips.

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