generate_video

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

Discloses async behavior and model differences but omits details on failure modes, timeouts, auth requirements, or rate limits. No annotations exist to compensate, so description carries full burden but falls short.

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, no redundancy. Front-loaded with the core action and key details. Every word earns its place.

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?

Adequate for a tool with thorough schema descriptions, but lacks examples or guidance on parameter combinations. No output schema means description should clarify return value further, which it does minimally.

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%, so the schema itself documents all parameters. The description adds minimal extra context beyond listing model capabilities, so 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?

Clearly states it generates a video asynchronously from text or images and returns a task ID. Lists supported models, distinguishing it from sibling tools like generate_image_async and get_async_result.

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?

Indicates async nature and need to poll for results, hinting at use with get_async_result. Does not explicitly state when not to use or compare with synchronous alternatives like generate_and_download_video.

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