set_clip_speed

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

No annotations are supplied, so the description carries the full burden. It says nothing about whether the change is destructive/non-reversible, whether linked audio clips are affected, what the defaults are for ripple/reverse/maintainPitch, or what happens when clip durations shift on the timeline.

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?

A single front-loaded sentence with the verb+resource first and concrete examples second; nothing is wasted or padded.

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 7-parameter timeline mutation with no annotations and no output schema, the description is far too thin. It omits ripple/reverse/maintainPitch behavior, the effect on timeline layout, and return/failure behavior, leaving the agent to reconstruct semantics from the schema alone.

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 all seven parameters are already documented in the schema; the baseline is 3. The description adds only the notion that 'speed' also controls duration (speed ramp), which is a marginal gain over what the schema states.

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 and resource ('Change the speed/duration of a clip') and adds examples (speed ramp, slow-mo) that pin down the intent. It implicitly contrasts with get_clip_speed and freeze_frame but never names a sibling, so differentiation is left to inference.

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 parenthetical examples imply when the tool is useful (retiming, slow motion), but there is no explicit guidance on when to use this versus get_clip_speed, freeze_frame, or slip/slide tools, and no prerequisites are stated.

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