Render an animation to APNG

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

No annotations are present, so the description carries the disclosure burden. It adds useful behavioral detail such as transparent background by default and full alpha support. However, it does not mention side effects like file creation, output path defaults, or overwrite behavior, leaving some important gaps.

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 focused sentences: the first states the function, the second gives format differentiation and a concrete use case, and the third notes the default transparency behavior. Every sentence earns its place with no 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?

This is a 12-parameter render tool with no annotations and no output schema. The description covers basic purpose and a key differentiator, but omits important invocation details such as output path defaults, state machine vs animation selection, and interactions with transparent/background. It is adequate for tool selection but not for full correct invocation across all options.

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 75%, so the schema handles most parameter meanings. The description adds context around transparency defaults but does not explain undocumented params like height, artboard, or stateMachine. It provides some added value but is not heavily compensating.

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?

Clearly states it renders .riv animations or state machine playback to APNG, naming the exact resource and output format. It also distinguishes itself from GIF by highlighting 24-bit color and alpha transparency, which separates it from sibling tools like riv_render_gif.

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?

Provides a concrete use case comparison with GIF, noting APNG's support for full alpha transparency and GitHub README compatibility, which helps an agent decide when to choose this tool. It does not explicitly exclude alternatives like video or sprites, but the context is strong.

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