capcut_set_clip_speed

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

With no annotations provided, the description must carry the behavioral disclosure burden. It adds useful context about pitch preservation and the effect on voices, but it does not mention whether the change is reversible, whether it applies to both video and audio tracks, or what the agent can expect after calling the tool.

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, focused sentence that front-loads the core action and uses concrete examples. Every element earns its place, and there is no redundant or generic filler.

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 moderately simple mutation tool with all parameters fully documented and no output schema, the description covers the essential behavior and the key optional behavior (pitch preservation). It is slightly incomplete in that it does not set expectations for post-call results, but the core information an agent needs to call it correctly is present.

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 description adds illustrative examples for the speed parameter and explains why preserve_pitch matters, but it does not add significant meaning beyond what the schema already 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?

The description states a precise verb ('Sets playback speed multiplier') and a clear resource ('clip'), with concrete examples that make the operation unmistakable. It is easily distinguished from siblings like trim_clip or add_transition, which target different editing operations.

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 description gives practical examples of when to use various speeds (slow-mo, talking head, time-lapse), which implies usage context. However, it does not explicitly state when not to use this tool or how it compares to alternatives like trim_clip or add_audio_fade.

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