clip_video

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

Discloses asynchronous nature (job takes 10–30 minutes), notification method (email), and agent check via get_clip_status. No annotations exist, so description carries burden and does well.

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?

Three sentences, each containing essential information: purpose, parameter handling with defaults, job duration and follow-up. No fluff.

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?

Missing immediate return value (likely a job ID), error conditions (e.g., invalid video URL or duration). With no output schema, description should cover what the tool returns. Also no mention of permissions.

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?

With 0% schema coverage, description adds value by explaining that missing parameters should be asked from user and providing default values. However, it does not explain enum options or video_url format constraints.

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 'Start a video-clipping job,' specifying the verb and resource. It distinguishes from sibling tools like get_clip_status (status) and download_clip (download).

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?

Provides clear guidance on when to use: when user wants to clip a video. Instructs agent to ask for missing parameters and provides defaults. Mentions alternative tool get_clip_status for status checks, but no explicit exclusions.

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