reverse_clip

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

Description adds only an implementation detail ('Uses QE DOM'), not behavioral traits. Annotations already indicate mutation (readOnlyHint false) but the description lacks details on side effects, reversibility, or impact on audio/duration.

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 sentences with no fluff. The second sentence ('Uses QE DOM') is of questionable value but does not harm conciseness. Slightly better than minimal.

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 simple 2-parameter tool with full schema coverage and annotations, the description adequately states the core function. However, it omits context like what happens to existing effects or whether reverse is applied immediately, making it minimally complete.

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 both parameters are described in the schema. The description adds no additional meaning beyond what the schema provides, resulting in a baseline score of 3.

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?

Description clearly states the action: 'Reverse a clip's playback direction', which is a specific verb+resource. It distinguishes from siblings like 'speed_change' by focusing solely on reversing direction, though it could explicitly contrast with similar 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?

No guidance on when to use this tool vs alternatives. The description does not mention prerequisites or scenarios where reversing is preferred over other clip adjustments like speed change.

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