OpenAI Videos Remix

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

The description claims to 'Create a remix video job', which is a write/mutation operation, contradicting the annotation readOnlyHint=true. This is a serious inconsistency (annotation_contradiction=true). The description also doesn't disclose potential side effects beyond creation, such as cost implications or state changes.

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?

Two sentences efficiently convey purpose and return format. The first sentence immediately states the core action, and the second explains the output. No extraneous information.

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 essential aspects: what the tool does, the source video, and the return structure. However, it omits details about the job object shape (no output schema), and the 'structuredContent' term is not explained. Despite this, it provides sufficient context for typical usage.

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?

All 7 parameters have descriptions in the input schema (coverage 100%), so the description adds minimal additional meaning. It references return format but does not elaborate on parameter specifics; baseline 3 is appropriate as schema already carries the burden.

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 ('Create a remix video job'), the resource ('from an existing video_id'), and the result (returns job object and optionally assets). It effectively distinguishes from sibling tools like openai-videos-create or openai-videos-retrieve by specifying the remix operation on an existing 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 identifies the tool's purpose but does not provide explicit guidance on when to choose it over alternatives (e.g., openai-videos-create for new videos) or when not to use it. No prerequisites or conditions are stated, leaving the agent to infer from context.

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