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

No annotations, so the description carries the burden. It usefully signals the operation is non-destructive ('save a new copy') and runs in-browser with higher credit cost, but it says nothing about output format, quality, or limits of the flip itself, and the pricing boilerplate dominates.

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 well in the first sentence, but a large block of generic pricing/credit boilerplate follows that is not specific to this tool and dilutes the signal. It earns partial credit for the clear opening.

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 no-parameter tool with no output schema, the description covers what it does and that it produces a new copy, which is adequate. However, the credit text is noise and the actual transformation details (quality, formats) remain unaddressed.

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 tool has zero parameters, so the baseline is 4. The description's mention of direction (left-right, top-bottom, both) is applied in the editor rather than as schema inputs, which could be clarified but isn't required given the empty schema.

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+resource: 'Flip Video — Mirror a video left to right, top to bottom, or both,' which conveys the transformation precisely. It doesn't explicitly name the sibling it differs from (mio_video_rotate), but the mirror semantics implicitly separate it from rotation.

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?

'Choose the direction in the video editor and save a new copy' implies the workflow but gives no explicit when-to-use or when-not/difference vs. rotate or crop. The remaining text is pricing/credit information rather than selection guidance.

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