create_video

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

With no annotations, the description carries the full burden. It discloses the async nature (returns a job object, monitor via status/webhooks) and hints at the workflow. This goes beyond basic, though it omits potential details like rate limits, which are not essential for a simple create operation.

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?

Three sentences, all informative and non-redundant. Front-loaded with the primary purpose, followed by return value and monitoring guidance. No 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?

For a create tool with 5 params and no output schema, the description sufficiently covers the purpose, async workflow, and how to monitor completion. It could elaborate on response fields, but get_video_status is mentioned for that. Overall, it is well-rounded for its complexity.

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 description coverage is 100% with detailed descriptions for all 5 parameters. The description adds no parameter-specific guidance beyond the schema, so the baseline 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 'Start a new video generation job with Sora', which is a specific verb+resource. It distinguishes from siblings (delete_video, get_video_status, download_video, list_videos, remix_video) by focusing on creation, and adds the return of a job object.

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?

Provides clear context as the entry point for video creation and explicitly directs the user to poll get_video_status or use webhooks for monitoring. However, it does not explicitly state when not to use this tool versus alternatives, so it lacks explicit exclusions.

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