ae_render_headless

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

No annotations are provided, so the description carries the behavioral disclosure burden. It usefully reveals that the render is headless and does not require After Effects to be open, but it does not disclose whether the call blocks until rendering completes, whether it returns progress/output, or what side effects occur beyond producing the output file.

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 concise sentences deliver the core purpose and the most important behavioral distinction without wasted words. The front-loaded 'Render a composition directly via aerender' immediately tells the agent what the tool does, and the second sentence adds a valuable clarification about After Effects not needing to be open.

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 8-parameter tool with no output schema and no annotations, the description covers the key headless-render context but leaves out runtime behavior such as whether the command is synchronous, how completion is signaled, or what happens on render failure. The schema covers parameters, so the main gap is execution behavior rather than invocation 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?

The input schema provides 100% description coverage for all 8 parameters, so the schema already explains project_path, comp_name, output_path, frames, templates, and aerender_path. The description adds no parameter-specific meaning, but the baseline of 3 is appropriate because the schema handles the heavy lifting.

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 states a specific action ('Render a composition') and the mechanism ('directly via aerender, command-line, no UI required'), which clearly differentiates it from UI-based siblings like ae_start_render and ae_add_to_render_queue. The added note that 'After Effects does NOT need to be open' reinforces the headless scope and removes ambiguity.

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?

The description provides clear context for when this tool is appropriate: headless, command-line rendering without the After Effects UI. It does not explicitly name alternatives or exclusion criteria, but the 'no UI required' phrasing strongly implies the intended use case versus queue-based or UI-driven render tools.

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