ue_render_sequence

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

With no annotations provided, the description carries full burden. It discloses it runs in UnrealEditor-Cmd headless, is asynchronous (start and check status), and warns that without config, output may be missing. It could mention return value or non-destructive nature explicitly.

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 well-structured: first sentence states purpose, then context, then Args list. It is appropriately sized for the complexity, though slightly verbose. Front-loaded with key information.

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?

While it covers purpose, behavioral context, and most parameters, it does not describe the tool's return value (e.g., success indicator, job ID). Given no output schema, this is a gap. It also omits two parameters.

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 has 0% description coverage, so the description adds significant value. It explains 7 of 9 parameters (e.g., config format, resolution default, output_dir default). engine_root and engine_version are undocumented, but coverage is high and explanations are clear.

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 with Movie Render Queue in background. The verb 'Renderizza' and resource 'Level Sequence' are specific, and it distinguishes from sibling tools like ue_render_status by focusing on initiating renders.

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?

It explains the tool runs in a headless process to avoid blocking the editor, and directs to ue_render_status for progress. While it doesn't explicitly list alternatives or exclusions, the context is sufficient for when to use this tool.

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