Render the final movie for a project

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

Discloses async nature, returns jobId, cost, and assembled components. No annotations provided, so description bears full burden. Lacks details on error conditions, destructive potential (though likely non-destructive), or rate limits. Adequate but not comprehensive.

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: purpose stated first, then async/cost details. Efficient and front-loaded. Could benefit from slightly more structure but is good for its length.

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?

No output schema; description mentions return type (jobId) and polling via list_movies. Covers async and cost. Does not explain output format or job lifecycle beyond polling. Adequate but not exhaustive.

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 low (33%); only aiGeneratedLabel has description. Description adds that settings fall back to project defaults, but does not explain meaning of nested settings properties (duration, resolution, etc.) beyond enum values. Minimal added value for 3 parameters (one nested object).

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?

Description clearly states the tool assembles timeline into final video with specific elements (clips, music, watermark, overlays). This verb+resource combination distinguishes it from sibling tools like add_timeline_audio or generate_clip, which handle individual components.

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 some context: only projectId required, settings fallback, async behavior, cost. However, no explicit guidance on when to use this vs alternatives (e.g., generating a clip vs rendering full movie). Missing exclusions or prerequisites.

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