render_shot_preview

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

With no annotations at all, the description carries the full behavioral burden. It implies a mutation (creating a 'new preview version') but never states that this is likely a long-running async job requiring polling via get_job_status, what permissions or prerequisites are needed, whether the source version is preserved, or how failures surface. For an 8-parameter render tool with zero annotation coverage, this is a substantial disclosure gap.

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?

A single front-loaded sentence with no filler, which is structurally sound. It is arguably under-specified rather than bloated, but there is no wasted text to penalize.

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?

An output schema exists, so return values need not be explained, but that is the only mitigating factor. For a tool with 8 undocumented parameters, no annotations, and a sibling get_job_status suggesting asynchronous execution, the description leaves critical operational context missing.

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% across 8 parameters, so the description must compensate and largely fails to. Only a faint hint connects 'review sequence' to frame_start/frame_end and 'new preview version' to source_version; project_root, request_id, and resolution_x/y receive no semantic treatment whatsoever.

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 gives a specific verb (render) and resource (a review sequence rendered into a new preview version), which is enough to distinguish it from the closely named sibling render_shot_final by signaling 'preview' rather than 'final'. It stops short of any explicit sibling differentiation, so it sits at a clear-but-undifferentiated 4.

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 statement of when to use this tool versus render_shot_final or render_character_review, which are the obvious alternatives for a render request. The agent is left to infer the preview/final distinction entirely on its own.

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