set_render_job

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Define an export/render job'. It does not state whether this mutates state, overwrites an existing job, persists anything, or actually produces media. 'Define' hints at non-execution, but the operational behavior remains opaque.

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?

One tight, front-loaded sentence with no filler, and the key preset constraint is placed prominently. It is appropriately short for what it communicates, though it is somewhat underspecified.

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?

Despite having five parameters, no annotations, and no schema-level parameter descriptions, the description provides only a minimal task statement. It does not cover the job lifecycle, parameter semantics, or how this differs from run_render, leaving an agent with materially incomplete information for a reliable call.

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 0%, so the description should compensate by explaining parameters. It adds only the allowed preset values; it does not explain job_id, input_path, extra_args, or output_path, nor note that job_id and input_path are required.

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 identifies a concrete action ('Define') and resource ('export/render job'), and enumerates supported presets (h264_mp4, prores, webm), so an agent can tell it configures a render job rather than merely examining one. It does not explicitly contrast itself with the sibling run_render, so it misses the top score.

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?

There is no guidance about when to call set_render_job relative to run_render or other sibling tools, nor any mention of prerequisites such as an existing input file or job lifecycle. The intention to prepare a job before rendering is implied, but that sequencing is left entirely to inference.

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