list_videos

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

There are no annotations provided, so the description carries the burden of conveying safety. The verb 'List' implies a read-only operation with no destructive side effects, and 'pagination support' hints at paged responses. However, it doesn't explicitly state the return format, default ordering, or any account-specific caveats, leaving some behavioral aspects implicit.

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, front-loaded sentence that wastes no words. It conveys the essential information immediately.

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 straightforward list operation, the description covers the core purpose, scope, and pagination feature. The schema documents all parameters. However, with no output schema, the description does not describe the return shape, but this is not essential given the tool's simplicity.

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 input schema already provides 100% coverage with descriptions for all three parameters (after, limit, order), including defaults and constraints. The description reinforces the concept of pagination but adds no additional parameter-specific meaning beyond what the schema offers, warranting the baseline score.

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 ('List'), the resource ('video generation jobs'), the scope ('for your account'), and a key feature ('pagination support'). This distinguishes it from sibling tools like get_video_status or delete_video.

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 indicates this tool is for listing all video generation jobs, which is the natural use case. However, it does not explicitly mention when to prefer this over alternatives, such as get_video_status for individual jobs, so it stops short of full alternatives guidance.

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