list_videos

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

The description goes well beyond the readOnlyHint annotation by disclosing the pagination mechanism (passing 'after' from 'last'), the exact response fields (id, status, progress, etc.), and the iteration pattern with 'has_more' and 'last'. This richly describes the tool's behavior without contradicting the annotations.

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 well-structured with a clear opening line, a 'Returns' section, parameter explanations, and a pagination example. Every sentence contributes useful information, and the format makes it easy to scan. It is appropriately sized for the tool's complexity.

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 there is no output schema, the description thoroughly covers what the tool returns (data, has_more, last) and how to paginate through results. It also mentions the included statuses and model fields, making it complete for an agent to understand and invoke the tool correctly.

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?

Despite 0% schema description coverage, the description fully compensates by explaining each parameter: 'limit' with default/max, 'after' as the pagination cursor from the previous response, and 'order' with its enum values. It also provides a concrete pagination example that demonstrates how to use these parameters together.

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 opens with 'List all video jobs in your OpenAI account,' which uses a specific verb ('List') and resource ('video jobs in your OpenAI account'), clearly distinguishing it from the sibling tool 'list_local_videos' by explicitly referencing the account scope. It also mentions pagination support, which is a key functional differentiator.

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 clearly states its purpose and provides detailed usage context for pagination, but it does not explicitly mention when to avoid this tool or which sibling tool to use instead (e.g., 'for local videos, use list_local_videos'). The phrase 'in your OpenAI account' implies the scope, but lacks an explicit contrast or alternative recommendation.

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