Render a single frame to PNG

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

With no annotations provided, the description carries the full burden. It discloses that the image is returned inline and saved to disk, which is a key side effect. However, it does not mention overwrite behavior, file permissions, or that state machine rendering may produce different results than linear animation.

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 two short sentences, immediately stating the core function and output behavior. No unnecessary words or redundancy.

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?

For a tool with 9 parameters and multiple render siblings, the description is minimal. It covers the basic output behavior but does not explain how to choose between state machine and animation, or how this tool differs from other render tools, leaving some 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 78%, with most parameters described, but width and height lack descriptions. The description itself adds no parameter-level detail beyond what the schema already provides, so it neither compensates for the gaps nor adds extra meaning.

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 clearly states the tool renders one frame of a .riv animation or state machine to PNG, using a specific verb and resource. This distinguishes it from sibling tools like riv_render_gif, riv_render_apng, and riv_render_video that handle animated output.

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 phrase 'one frame' implies use for static captures, but no explicit guidance is given on when to choose this over the animated/render siblings. No alternatives are named and no exclusion criteria are provided.

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