Render frame

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

Annotations only carry destructiveHint=false; the description shouldered the rest and does well on execution traits (headless, deterministic, file naming, contact-sheet defaults). The color-management section is unusually candid about fallbacks and the `colorWarning` escape hatch. However, it omits cost/latency expectations for multi-frame renders up to 32 items and says nothing about mutation of disk state beyond created parent directories.

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?

Purpose is front-loaded in the first clause, and each subsequent sentence covers a distinct decision (single vs multi-frame, contact sheet, analysis, color pipeline). It is a single dense paragraph of ~150 words that would scan faster as a short list, and the color-management sentence is long enough to bury its actionable tail.

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?

With 11 parameters, a nested object, and no output schema, the description carries the response contract itself: it names `frames`, `analysis`, `colorPipeline`, and `colorWarning`, and explains what lands on disk. An agent has everything needed to call it correctly and interpret what comes back.

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 coverage is 100%, so the baseline is 3; the description still adds value by explaining the interaction between `time`/`times` (mutually exclusive, index-aligned output), how `outPath` doubles as a naming stem, and why `colorManaged: off` yields dark/wrong-looking results. These are behavioral consequences rather than restatements, though much of the per-parameter detail is already in the schema.

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?

Opens with a specific verb+resource+output format ("Render one or more frames to PNG") and immediately frames the intent with a metaphor plus a concrete use ("visually verify edits", "pair with mutations for a visual feedback loop"). This clearly separates it from the sibling info/context tools, none of which produce pixels.

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?

Explicit routing rules: use `time` for one frame, `times` for several in ONE call for motion checks, `contactSheet` when a motion check should be one image, `analyze` when you want numeric checks instead of eyeballing. It also states the pairing pattern (mutations + render = feedback loop), so an agent knows when to reach for it.

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