generate_video

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

No annotations provided; description discloses async job submission and ID return, but lacks details on side effects, auth requirements, rate limits, or success/failure conditions.

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 two concise sentences, efficient and front-loaded with key behavioral 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?

With 11 parameters, no output schema, and no annotations, the description covers the core async pattern but omits details on many parameters and return value specifics beyond the ID.

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 45% (5/11 parameters have descriptions). The description does not add meaning for undocumented parameters like seed, resolution, aspect_ratio, generate_audio, etc., and does not compensate for the low coverage.

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 tool submits a video generation job, returns its ID immediately, and does not wait for the render. It also directs to poll with get_job, distinguishing from synchronous siblings.

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 explains async behavior and directs polling, but does not explicitly compare with generate_image or list prerequisites like model selection.

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