render

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. It does mention that rendering is deterministic and that QC is optional, which adds some context, but it omits important behavior such as whether a file is written, whether a project must be loaded, and what happens to existing outputs. This is a significant gap for a tool with no annotation support.

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 a single sentence that front-loads the main action and avoids filler. It is appropriately short, though the parenthetical 'deterministic' could have been expanded into a more useful behavioral note.

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 the existence of several render-related siblings, no annotations, and no output schema, the description leaves critical gaps: it does not explain the output parameter, dry-run semantics, or how this render differs from render_farm/render_proxy. An agent would likely need external knowledge to use the tool correctly.

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 must compensate for the undocumented parameters. It only hints at run_qc_after via 'optionally QC it'; output and dry_run remain unexplained. The description does not add enough meaning to help an agent fill parameters correctly.

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 uses a specific verb and resource: 'Compile the timeline to video', which clearly states the core operation. It also adds a useful distinguishing trait ('deterministic') and mentions optional QC. However, it does not explicitly differentiate from sibling tools like render_proxy or render_farm, so it is clear but not fully differentiated.

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 gives no guidance on when to choose this tool over alternatives such as render_proxy, render_farm, or render_farm_dry_run. It also does not clarify when dry_run or run_qc_after should be used.

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