OpenAI Videos Retrieve Content

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

The description claims the tool writes a file under MEDIA_GEN_DIRS, which is a write operation, but annotations declare readOnlyHint=true. This is a contradiction. No other behavioral traits are disclosed beyond the contradiction.

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 of about 25 words, front-loaded with the purpose. No redundant 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?

The description covers the main purpose and parameter details, but lacks specifics on output structure (e.g., shape of resource_link vs resource) and file path conventions. With no output schema, this leaves gaps.

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%, baseline 3. The description adds meaning: 'video asset' maps to variant enum, explains tool_result param, and adds 'completed job' context for video_id, going beyond schema descriptions.

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 uses a specific verb 'retrieve' and resource 'video asset', clarifying the exact type (video/thumbnail/spritesheet). It distinguishes from siblings like 'google-videos-retrieve-content' by being OpenAI-specific, and adds details about writing to MEDIA_GEN_DIRS and returning content blocks.

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 explicitly states 'for a completed job', providing context on when to use. However, it does not explicitly contrast with siblings like 'openai-videos-retrieve' or 'openai-videos-list', leaving some ambiguity.

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