Render animation frames

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

With readOnlyHint=true already covering safety, the description adds useful behavioral context: ~4 s runtime, caching, disabled MSAA, no physics warm-up, and a contact-sheet return. It still leaves cache invalidation and parameter-dependent behavior unstated, but the added operational detail is meaningful.

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?

Two tightly written sentences front-load the operation and then append the runtime/quality caveat. No filler; the caveat is directly relevant to tool selection.

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?

The description covers selection-level behavior, output type, performance, and quality limits, which is useful given no output schema. For a 9-parameter tool with low schema coverage, however, it omits guidance on most invocation parameters, so it is not fully complete.

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 only 33%, and the description adds no explanation of fps, maxFrames, refresh, skin, project, or scale beyond the vague mention of rendering an animation. The agent must infer most parameter meaning from names and bounds alone.

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 opens with a specific verb ('Renders') and resource ('an animation'), names the concrete output ('contact sheet'), and distinguishes this from final video output. An agent can identify it as a preview-render tool without opening the schema.

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?

It states the primary use case ('for checking') and an explicit exclusion ('not final video'), which tells the agent when this is appropriate. It does not name a specific sibling to use for final video, so routing relies on the agent's own comparison.

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