Set clip speed

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

With no annotations provided, the description carries the full behavioral burden and does well: it discloses the ratio range and mapping, repitch vs stretch semantics, lockTempo's tempo-following formula, and clip-tempo detection via beat tracking or explicit tempo. It still omits permissions, undo behavior, and side effects of mutating a clip, which keeps it from a 5.

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 dense and front-loaded: the first sentence defines the core action, the next explains mode, and the last explains tempo locking. Every sentence earns its place without repetition or 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 an 11-parameter mutation tool with full schema descriptions but no annotations or output schema, the description covers the essential operational semantics and parameter interactions. It could be more complete by mentioning side effects, required permissions, or undo implications.

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 baseline is 3. The description adds meaningful semantics beyond the schema for key parameters, including ratio-to-length mapping, mode defaults and behavior, and the relationship between lockTempo, tempo, and detected clip tempo.

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 opens with a specific verb and resource: 'Sets a clip's playback speed.' It immediately distinguishes the tool from siblings like clip_gain and clip_fades by targeting playback speed, so an agent can identify its function without opening the schema.

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 explains operational choices such as mode selection and lockTempo behavior, implying when to use those features. However, it does not explicitly state when to use clip_speed versus other editing tools, nor does it describe when not to use it or what alternatives exist.

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