Crop video

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

With no annotations provided, the description carries the full burden. It explains that x/y is the top-left corner and that the region is kept, but does not disclose important behavior such as whether output_path is required, how the output file is written, whether audio is preserved, or what happens if the crop boundaries exceed the frame.

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 two concise sentences, front-loaded with the main action and coordinate clarification. There is no redundancy or wasted words.

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?

Despite having 6 parameters and no output schema or annotations, the description only covers the core cropping concept. It omits critical context such as the role of the optional output_path, validation behavior, and what the tool returns or writes, leaving the agent with unanswered questions for a tool of this complexity.

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 the baseline is 3. The description adds value by clarifying that x/y refers to the top-left corner of the region to keep, which complements the schema's per-parameter descriptions and removes ambiguity about coordinate meaning.

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 tool crops a rectangular region from the video frame, using a specific verb and resource. It also differentiates from sibling tools like resize_video and trim_video by explicitly mentioning the crop region and coordinate origin.

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?

Usage is implied: use this when you need to keep a rectangular portion of the video. However, there is no explicit guidance on when to use this versus alternatives like resize_video or trim_video, nor any exclusions or prerequisites.

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