capcut_set_speed_curve

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 only says 'Apply' and gives preset names; it does not disclose whether this mutates the draft in place, overwrites an existing speed curve, changes clip duration, requires saving, or what happens on invalid input.

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, front-loaded sentence with no filler. The preset examples aid readability, though they mostly duplicate the schema enum, so the sentence could arguably be shorter or more informative.

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?

Given three required parameters, no annotations, no output schema, and a relatively specialized operation, the description is under-specified. An agent cannot confidently know what `draft` refers to, how custom curves are represented numerically, or what effects or errors to expect after invocation.

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 67%, which is moderate, and the description adds no parameter-specific meaning. It does not clarify the opaque `draft` parameter, nor does it explain the coordinate space for custom array-based curves (e.g., x/y ranges or normalization). The curve preset examples partly duplicate the schema enum values.

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 verb ('Apply'), resource ('dynamic speed ramping/curves'), and target ('video clip'), and the preset examples make the intent unmistakable. It distinguishes itself from most siblings by subject matter, though it does not explicitly name an alternative or contrast it with similar apply-style tools.

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 explicit guidance on when to use this tool versus alternatives like capcut_apply_animation or capcut_trim_segment. The description implies 'use when you need speed ramping,' but it does not state conditions, exclusions, or prerequisites such as whether the segment must already have a speed curve or whether a draft must be open.

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