Generate a video

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

With no annotations, the description carries full burden. It discloses async behavior (wait=false returns task id), duration constraints (8s, 6s/10s), and model-specific features. Missing details on rate limits, error responses, or cost implications, but key behaviors are well covered.

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 lengthy but front-loaded with main purpose and model list. Every sentence adds value: model scope, image-to-video, multimodal options, duration, async. Could be slightly more concise, but structure is logical and information-dense.

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?

Given 16 parameters, no output schema, and no annotations, the description covers all crucial aspects: model support, image-to-video, keyframe control, multimodal references, async behavior, model-specific durations. Missing error handling or output format, but overall highly complete for a complex tool.

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 88%, but description adds significant meaning beyond schema: explains image+last_frame as start+end keyframe interpolation, Seedance 2 multimodal references, wait parameter async behavior, and resolution constraints. This substantially aids correct parameter usage.

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 with a Pixmax model, lists multiple supported models, and distinguishes from sibling tools like generate_image and generate_audio. The verb 'generate' plus resource 'video' with specific model context makes the purpose unmistakable.

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 explicit guidance on when to use image, last_frame, reference_videos, reference_audio, and wait parameters. Differentiates between Seedance 2 multimodal capabilities and other models. Includes duration notes for Veo and Hailuo. No explicit 'when not to use', but the level of detail compensates.

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