OpenAI Videos Retrieve

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

The description says 'Retrieve' which aligns with the readOnlyHint annotation. However, it does not add any behavioral details beyond annotations, such as what happens if the job ID is invalid or whether the operation is idempotent (annotation says false but not explained). Adequate but not enhanced.

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?

One sentence, 10 words, front-loaded with the key action and resource. No extraneous information. Efficient and to the point.

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 simple retrieval tool, the description is minimally complete. It states what it does, but lacks details about response format, error handling, or differentiation from content retrieval. Given the absence of output schema, some additional context would be beneficial.

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 has 100% coverage with a single parameter 'video_id' described as 'Video job id.' The description adds no further meaning beyond the schema. Baseline score of 3 is appropriate.

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 'Retrieve a video job by id' which is a specific verb-resource pair. It distinguishes from siblings like 'openai-videos-list' (list all) and 'openai-videos-retrieve-content' (get content) by focusing on the job itself.

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?

No usage guidelines provided. The description does not specify when to use this tool over alternatives, such as when to retrieve vs. list, or what prerequisites (e.g., a valid job ID) are needed. An explicit note about using this tool when having an ID would help.

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