list_videos

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions filtering and pagination but doesn't specify what filtering options exist, whether results are sorted, if there are rate limits, authentication requirements, or what the return format looks like. For a list operation with no annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence that states the core functionality upfront. It's appropriately sized for a simple list tool, though it could potentially be more structured by separating filtering and pagination aspects into distinct clauses for clarity.

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?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what information is returned about each video job, how filtering works, what fields are available, or what the response structure looks like. For a tool that presumably returns multiple video records, this leaves the agent with insufficient context about what to expect.

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 schema description coverage is 100%, with both parameters well-documented in the input schema. The description adds minimal value beyond the schema by mentioning 'optional filtering and pagination' but doesn't provide additional semantic context about parameter usage, relationships, or constraints beyond what's already in the structured 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?

The description clearly states the tool's purpose as listing video generation jobs with filtering and pagination capabilities. It specifies the resource (video generation jobs) and verb (list), but doesn't differentiate from sibling tools like 'get_video_status' which might also retrieve video information.

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 through 'optional filtering and pagination' but doesn't explicitly state when to use this tool versus alternatives like 'get_video_status' for individual videos or 'create_video' for new jobs. No explicit when-not-to-use guidance or alternative recommendations are provided.

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