create_render_job

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false. The description adds valuable behavioral detail beyond that: the job is added to the editor's transient render queue, persists there, and gets a primary configuration if missing, which tells the agent about state mutation without destruction.

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 front-loaded with the core action and includes a useful structured Returns block. However, the parenthetical map example '(e.g. "/Game/Maps/MyMap.MyMap")' is awkwardly orphaned at the end, detached from the sentence about setting the map, which slightly hurts structure.

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 mutating tool with a full annotation set and no output schema, the description covers what is created, where it persists, and enumerates the return fields. It is nearly complete, needing only clearer routing guidance relative to execution-oriented siblings.

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 100%, so both optional parameters (job_name, map_path) and the required sequence_name are already fully documented in the schema. The description only restates that it points at the given sequence and optionally sets the map, adding no syntax or format detail beyond the schema; baseline 3 is appropriate.

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 states a specific verb (allocates/creates) and resource (a UMoviePipelineExecutorJob in the Movie Render Queue), naming the concrete engine type added. It clearly distinguishes itself from siblings like cancel_render_job, delete_render_job, and render_sequence_to_movie by describing job creation and configuration setup.

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 provides context by noting '(headless authoring)', which implies when the tool applies, and mentions it 'ensures it has a primary configuration'. However, it never names alternatives such as render_sequence_to_movie (which would actually execute the render) or configure_render_output, so the agent must infer when to pick this over them.

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