render-aerender

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

With no annotations provided, the description carries full transparency burden. It discloses background/headless execution, the save-first default, projectPath override, immediate return, and waitMs behavior. It omits error-handling details but covers core behavioral traits.

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 compact, front-loaded with purpose, and each sentence adds value: purpose, differentiation, requirement, default behavior, and return semantics. No redundant text.

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?

Given the 9-parameter schema and no output schema, the description sufficiently covers main usage, prerequisites, async behavior, and follow-up. It does not spell out the return value format, but 'Check progress with render-status' implies a handle is returned.

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 100%, so baseline is 3. The description adds prose context for projectPath and waitMs, clarifying how they alter execution. It also explains the saveFirst default, enriching the schema's 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 a composition to a file in the background using aerender, and explicitly contrasts it with start-render. This distinguishes it from siblings and gives a specific verb, resource, and execution mode.

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 explicit when-to-use guidance: 'Unlike start-render, this does NOT freeze your After Effects UI'. Also states the project-save requirement and directs the user to render-status for progress, effectively outlining a workflow.

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