clip_reset_speed

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

No annotations are present, so the description must carry the full burden. It states the operation ('revert') but does not disclose whether the action is destructive, whether it fails if no speed change exists, or whether it resets to original speed versus 1x. It also omits any side effects on other clip properties.

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?

Two concise lines with the main purpose front-loaded and no filler. The Args section adds necessary parameter detail without redundancy.

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 single-parameter tool, the description covers the operation and the key format, which is sufficient for basic invocation. However, it lacks any mention of error behavior or prerequisites, and without annotations or an output schema, a bit more behavioral context would be helpful.

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?

With 0% schema description coverage, the description compensates by explicitly defining the key parameter format as 'trackId:itemId'. This is essential for correct invocation and adds meaning beyond the bare schema type.

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 uses a specific verb 'Revert' and a clear resource ('a clip's speed change'), and it references the counterpart tool clip_set_speed, making its scope unambiguous. This distinguishes it from pitch-related siblings like clip_reset_pitch and clip_reset_pitch_speed.

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 implies usage when a speed change was previously applied via clip_set_speed, giving a clear trigger condition. It does not explicitly name alternatives or state when not to use it, but the reference to clip_set_speed provides enough contextual routing for an agent.

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