render

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

No annotations are provided, so the description carries the full behavioral burden. It hints that ffmpeg is invoked and that a file is produced, but says nothing about whether rendering is blocking or long-running, whether it overwrites out_path, or what permissions are required — meaningful gaps for a media-encoding mutation.

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?

Three short sentences, front-loaded with the action, then the enum values, then the return shape — no filler. It is terse to the point that 'version' remains undefined jargon, which slightly undercuts the economy.

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 needn't be spelled out (and the description repeats them anyway). The real gaps are behavioral: no indication of async vs blocking execution, overwrite behavior, or the meaning of the required version_id, which an agent needs before invoking a render job.

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 0% and the schema has no enum for preset, so listing 'original | reel_9x16 | yt_16x9' is genuinely additive information the agent cannot get elsewhere. However, version_id and out_path are left completely unexplained, including what an empty default out_path means.

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?

States a specific verb ('Render') plus resource ('a version') and names the underlying engine (ffmpeg), so the agent knows this produces a media file rather than metadata. It does not differentiate itself from siblings like edit or check, but the operation is unambiguous.

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 call render versus the sibling tools (edit, check, peek, diff), nor any prerequisite such as needing an existing version_id. The agent must infer usage entirely from the name.

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