vfx_render

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

With no annotations, the description carries the burden and discloses key traits: GPU rendering, non-destructive behavior ('The file is not changed'), per-cell stats, quality warnings, and backdrop choices. It still omits operational traits such as performance or auth requirements, which prevents a full 5.

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 front-loaded and dense with useful details, avoiding filler. Its semicolon-heavy style makes some mode distinctions harder to scan, but every sentence contributes information.

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 an 11-parameter rendering tool with nested sweep and no output schema or annotations, the description covers the essential modes, output stats, quality warnings, and non-mutation. It is not fully exhaustive about every parameter, but the schema supplies most remaining details.

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 high at 82%, so the baseline is 3, but the description adds meaningful semantics beyond the schema: the phases mode, the sweep object's purpose and defaults, and the backdrop options. It does not add much for ss, size, frames, margin, values, or duration, but the added nested-object guidance is valuable.

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 a specific verb and resource: 'Renders a node on the GPU and shows it as one image,' with concrete grid behavior. It indirectly distinguishes itself from write-oriented siblings by saying 'The file is not changed,' though it does not name alternatives.

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 explains the default flipbook behavior, when phases are useful, and what sweep does, which implies usage contexts. However, it never explicitly says when to choose vfx_render over vfx_preview, vfx_bake, or other siblings, nor does it state exclusions.

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