rotate_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 of behavioral disclosure. It only states the operation, without revealing side effects (e.g., writes to output_path, whether input is preserved, codec/quality behavior, or any limitations). The description adds almost no context beyond the core action.

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 short sentence that front-loads the primary action. It is concise and every word contributes meaning, though it could be slightly more informative without losing conciseness. This is efficient but 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?

The tool has 4 parameters, no output schema, and no annotations. The description does not mention return values, file handling behavior, or any caveats. It is inadequate for an agent to fully understand the tool's behavior, especially given the lack of output schema and the presence of multiple sibling tools with overlapping scope.

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 description coverage is 50% (only input_path and output_path are described). The description gives a high-level mapping (rotate→rotation, flip→flip) but does not explain parameter semantics beyond what the enum values already show. It adds some value but does not fully compensate for the missing descriptions on rotation and flip.

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 clearly states the action (rotate and/or flip) and the resource (video). This is a specific verb+resource that distinguishes it from sibling tools like crop_video, resize_video, and convert_format, each of which targets a different transformation.

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 context—it is for rotating or flipping videos—but provides no explicit alternatives or when-not-to-use guidance. Since the tool's name and action are self-evident, the usage is implied rather than explicit.

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