generate_video

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

Discloses generation time (1-5 minutes) and that it returns a URL. However, no details on error handling, rate limits, or cost. Since annotations are absent, the description partially fills the gap but could be richer.

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?

Extremely concise with three sentences, no redundancy. Each sentence serves a purpose: defining capability, listing models, and noting runtime.

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?

Covers basic usage and output (URL) but lacks details on asynchronous behavior (e.g., polling vs. blocking), error states, or limitations beyond time. Adequate but not fully comprehensive.

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?

Adds context beyond schema descriptions, such as default model selection based on image_url presence and examples of supported models. The duration parameter is noted as model-dependent, providing valuable usage insight.

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 the tool generates videos from text or image input using specific models. It distinguishes itself from siblings by focusing on video generation vs. image generation or general model running.

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?

Implied usage based on input type (text vs. image) but no explicit guidance on when to use this tool over generate_image or run_model. Missing when-not-to-use or alternative recommendations.

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