cineflow_video_render

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

With no annotations, the description carries the full behavioral burden, and it does disclose one real behavioral rule: a closed-mouth guard is enforced on non-dialogue clips, with an issue reference (#600). It omits other important traits for a render job, such as whether the call is synchronous or long-running, cost implications, failure/retry behavior, and what a result looks like.

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 short sentences, front-loaded with the core action and followed by the constraint, with no filler. The trailing '#'600 parenthetical is slightly cryptic but does convey provenance for the guard rule rather than padding.

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?

This is a nested-array, multi-clip video render tool with no annotations and no output schema, so the description must explain execution model, expected return, and parameter units — it covers none of these. Given 50% schema coverage and per-clip fields like duration and shot_index left undefined, an agent lacks enough context to call it confidently.

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 description coverage is 50%, with project_id and prompt/voice_track/keep_mouth_closed described in the schema but duration and shot_index undocumented. The description adds meaning by tying the 'closed-mouth guard' explicitly to the keep_mouth_closed flag and by naming the engines, but it does not explain duration units, shot_index semantics, or batch behavior of the clip_specs array.

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?

States a specific verb and resource ('Render motion video clips for shots') and names the underlying engines (MiniMax H3 / LTX 2.5), which is more than a restatement of the name. It does not distinguish itself from nearby render-adjacent siblings such as cineflow_frames_generate or cineflow_quick_photo_animate, so the boundary is left implicit.

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?

There is no when-to-use guidance: no statement of prerequisites (project init, asset availability, credit/plan requirements) and no indication of which sibling to use for still frames versus video versus export. An agent must infer usage purely from the tool name and the phrase 'for shots'.

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