reverse_video

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

No annotations are provided, so the description carries the full burden. It only restates the operation and discloses nothing about output format, side effects, whether the input file is modified, or how audio is handled. For a mutating tool this is a significant gap.

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 sentence with no waste, which is good for conciseness. However, it is under-specified rather than efficiently informative — brevity at the cost of essential guidance.

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?

With no output schema and no annotations, the description should explain return behavior, parameter requirements, and effect on audio. It does none of this, making the tool underspecified for reliable use.

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?

The schema has one parameter, input_video, with 0% description coverage. The description adds no detail about what the parameter should be (path, URL, video ID), accepted formats, or constraints. The variable name is suggestive but insufficient for correct invocation.

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 clear verb and resource: 'Reverse a video.' This is specific enough to distinguish it from many siblings like rotate_video or trim_video. However, it does not clarify nuances such as whether audio is reversed too or what 'reverse' means exactly.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention use cases, prerequisites, or exclusions, even though the sibling list includes related transformations like loop_video and change_speed.

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