cineflow_dialogue_tts

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

With no annotations, the description carries the full disclosure burden and largely drops it. It does not say whether existing rendered audio is overwritten, whether rendering is costly or slow, what permissions are needed, or what the response contains. For a tool that performs batch media rendering, that silence is a meaningful gap.

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?

A single front-loaded sentence with no filler; the render action and its scope come first and the rationale follows. It is efficient, though the brevity is achieved partly by omitting information the agent needs.

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?

There is no output schema and no annotations, so the description is the only source of behavioral context, and it does not say what comes back (audio file references, per-line durations, timing data) or how rendering interacts with project state. For a two-parameter tool with a nested input array, this is under-specified.

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 50%: project_id is documented in the schema, but the lines array and its item fields (speaker, text, emotion) have no description anywhere. The description's phrase 'dialogue audio lines' hints at the lines parameter but never explains the per-line structure, the meaning of emotion, or what happens to lines not supplied.

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 names a specific verb and resource: 'Render all dialogue audio lines for the project.' An agent knows this produces audio from dialogue text, and 'all' signals batch scope. It does not, however, differentiate itself from the sibling cineflow_quick_tts, so the boundary between the batch and quick paths 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?

The only usage signal is the downstream rationale ('to establish exact shot timing and audio pacing'), which implies this is a pre-timing step. There is no explicit when-to-use guidance, no statement of when to prefer cineflow_quick_tts instead, and no prerequisites such as whether voices must be configured first.

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