output

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. Exporting video/GIF/EXR/TIFF writes files and camera solves are expensive compute-bound operations, but the description says nothing about side effects, output locations, overwrite behavior, processing time, or required project state. Format names add only surface-level context.

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?

It is a single compact fragment with no filler, which is efficient, but the comma-separated feature dump is not front-loaded around the action/args contract and reads as an unordered keyword list rather than structured guidance.

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 40-action dispatcher with a free-form string action, an unbounded nested args object, no annotations, and no output schema, the description is far too thin. It should at minimum enumerate the action identifiers and the required shape of args; without that, correct invocation is guesswork.

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% and 'action' is an unconstrained string with no enum, while 'args' is an opaque nested object. The description lists some output formats but never enumerates the 40 valid action values or explains how args map to a given action, so an agent cannot construct a correct call from either source.

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 verbs and resources ('Render a frame', 'export video') and signals breadth with '[40 actions]', so the agent knows this is a rendering/export dispatcher. However, it never says what a single 'output' call actually does or how the 40 actions divide the space, and the tool name 'output' on its own would be meaningless without it. It is clear enough to categorize but not to distinguish precisely from siblings like 'color_science' or 'vfx3d'.

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 siblings (color_grade, vfx3d, project) and no exclusion criteria. '[40 actions]' implies the caller must pick an action, but neither the description nor the schema offers the action list, so no routing guidance is actually provided.

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