ae_addToRenderQueue

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

Annotations already declare this is a non-read-only, non-destructive, non-open-world mutation, so the safety profile is partially covered. The description adds that it enqueues a comp with specific templates and supports work-area or custom-range rendering, but it does not mention output overwrite behavior, queue side effects, or return behavior.

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 definition is a single dense sentence with the core action front-loaded and examples that earn their place. It is efficient, though the embedded template examples make it slightly harder to scan.

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 mutation tool with no output schema and limited annotation detail, the description covers the main inputs and enqueue action. It still omits important operational context such as whether the output path must already exist, what happens on overwrite, and what the tool returns.

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 17%, so the description carries extra burden. It usefully explains outputPath, outputModuleTemplate with examples, renderSettingsTemplate, and the work-area/custom-range option implied by start and duration, but it leaves the units and interaction of start/duration undefined and gives no renderSettingsTemplate examples.

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?

States a specific verb and resource: 'add a comp to the Render Queue', and names the key inputs (output path, output-module template, render-settings template, work area or custom range). It is clearly distinct from generic queue-management siblings like ae_renderQueue, but it does not explicitly name or differentiate any sibling tool.

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?

No when-to-use guidance is provided relative to alternatives such as ae_renderQueue, ae_queueInAME, or xapp_renderAEToPremiere. The description implies the operation but never states prerequisites or exclusions.

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