render_sequence_to_movie

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

Goes well beyond the annotations by disclosing the async execution model, that it returns immediately rather than blocking, that it spins up a PIE session, and that in headless contexts the job/config are still authored even if the render does not start. This is exactly the kind of behavioral context the structured fields do not carry.

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?

Front-loads the action ('Authors ... and starts the ... render') and then layers the async caveat efficiently. The Returns block is useful but slightly verbose; nearly every sentence earns its place, with minor redundancy between 'returns render_started immediately' and the return-field list.

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 mutation tool with no formal output schema, the description supplies a full return-shape listing plus the async and headless caveats, which is enough for correct invocation. It stops short of explaining the destructiveHint (what the render session affects) or preconditions, leaving a small gap.

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 sequence_name and map_path are already documented in the schema. The description references 'a sequence' and the 'default PNG output config' but adds no syntax or format detail for either parameter, so it does not exceed the 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?

States a specific verb+resource: 'Authors a one-off render job for a sequence and starts the (async) movie render', and pins the mechanism (RenderQueueWithExecutor, PIE executor). It does not, however, distinguish itself from closely-related siblings like create_render_job or configure_render_output, so the agent cannot route between them from this text alone.

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?

Usage context is implied by 'one-off' and the headless/non-interactive caveat, which tells the agent when the render may silently not start. But no explicit when-to-use vs create_render_job/configure_render_output guidance or prerequisites (e.g. save state, required PIE availability) are given.

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