render_video

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

No annotations provided, so description carries full burden. It discloses the 2-10 minute duration and that user confirmation is required, but does not mention whether it is destructive, rate limits, or side effects. It returns a progressUrl, which is helpful but lacks detail on the output structure.

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 well-structured sentences with no fluff. Front-loaded with core action and timing, then prerequisite and output. Every word is useful.

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?

For a complex, long-running tool with no output schema, the description is remarkably complete: it explains the process, time estimate, prerequisite step, required parameter condition, and what the response contains. Sufficient for the agent to use correctly.

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 100% so baseline is 3. The description adds value by explaining that user_confirmed_content must be true because the user already reviewed the HTML and dubbing script. Aspect_ratio default is already in schema.

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 that the tool triggers video rendering involving TTS, screen recording, and mixing, with a duration of 2-10 minutes. It specifies the prerequisite of get_render_preview and user confirmation, distinguishing it from sibling tools like re_render_video.

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?

Explicitly states that get_render_preview must be called first and user_confirmed_content must be true. This provides clear when-to-use and prerequisite guidance, ensuring correct invocation.

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