Create video render

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

Discloses that credits are reserved up front and returns a jobId for polling, beyond what annotations (none) provide. Good behavioral context without contradictions.

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?

Three information-dense sentences, front-loaded with the core action. Efficient but could be slightly more concise by avoiding repetition of parameter names already in schema.

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 all critical aspects: input options, return value, polling mechanism, credit reservation, and prerequisites (plan_creative_video, validate_project_json). Complete for a queueing tool with no output schema.

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 3. The description adds value by explaining the exclusive use of payload vs template, referencing validation functions, and detailing the template pattern. Slightly above baseline.

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 'Queue a video render' and specifies two distinct input methods (payload or template), distinguishing from siblings like create_image_render and create_bulk_render.

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 advises not to hand-compose payload for new creative content, and directs to use plan_creative_video, start_from_example, and validate_project_json. Provides clear when-to-use and when-not-to-use guidance.

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