ue_render_sequence

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explains that rendering runs in a separate headless process and that the force parameter can override an existing render. However, it does not detail side effects, error handling, or how results are obtained, nor does it confirm safety (e.g., destructive nature) beyond the background execution claim.

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?

The description is concise and well-structured: a single-sentence purpose, followed by a contextual note about headless vs in-editor, then a bullet-style parameter list with clear explanations. Every sentence adds value without redundancy.

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?

Given 9 parameters, no output schema, and no annotations, the description covers core behavior and most parameters. However, it omits two parameters entirely (engine_root, engine_version) and does not specify return values or error handling. The suggestion to check ue_render_status is helpful but incomplete for a fully autonomous agent.

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?

The input schema has 0% description coverage (only titles), so the description adds significant value. It explains 7 of 9 parameters with examples and defaults: uproject, sequence, config (stressing its importance), map_path, output_dir, resolution, and force. However, engine_root and engine_version are missing from the description, leaving them undocumented.

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 the tool renders a Level Sequence using the Movie Render Queue in background, headless via UnrealEditor-Cmd. It specifies the verb 'renderizza' and resource 'Level Sequence', and distinguishes from other tools like ue_render_status which is for checking status.

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 description explains when to use it: for rendering sequences that would otherwise block the editor. It advises consulting ue_render_status to monitor progress. It does not explicitly say when not to use it or provide alternatives, but the context of background vs in-editor rendering is clear.

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