Reverse a local H.264 video

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

Goes well beyond the annotations by disclosing output verification of timing and decoding, a silent-by-default audio policy, explicit AAC encoder requirements for keep_audio, the guarantee that requested sound is never silently dropped, and pre-decode geometry validation. These are exactly the behavioral details an agent needs before invoking a non-idempotent mutation.

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 purpose is front-loaded in the first sentence, and each subsequent sentence adds a distinct behavioral fact. It is somewhat dense with technical phrasing ('bounded packet audio processing'), but no sentence is wasted.

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 four-parameter mutation tool with no output schema, the description covers the critical behaviors: audio handling, geometry checks, verification, and environment prerequisites. It falls short only on quality-level semantics and on output_path overwrite behavior.

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 50%, and the description compensates strongly for keep_audio by explaining its default, its dependency on a native AAC encoder, and the no-silent-drop guarantee. The quality enum, however, remains undocumented in both schema and description.

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: reverse video frames into a re-encoded H.264 MP4, plus output verification. This clearly distinguishes it from siblings like abox_video_rotate, abox_video_trim, and abox_video_remux.

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 gives useful prerequisites ('Requires a local browser and native codecs') and clarifies the default silence behavior, but it never states when to choose this tool over alternatives such as abox_video_trim or abox_video_rotate. Usage is implied rather than explicitly routed.

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