add_to_render_queue

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

The description only restates the basic action. It does not disclose that the tool does not start rendering unless startImmediately is true, that it requires AME to be installed, whether it blocks, or what the return value indicates. With no annotations, the description carries the full burden but offers no behavioral context beyond the action.

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 one concise sentence that immediately front-loads the verb and resource. No words are wasted, making it highly efficient for its clarity.

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?

With 8 parameters, several related sibling tools, and no output schema or annotations, the description is far too minimal. It doesn't explain the typical queue-then-encode workflow, how to choose between presetName and presetPath, or what happens after adding a sequence, leaving significant gaps for an agent.

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 schema has 100% parameter description coverage, including explicit descriptions for presetName, sourceRange, and defaults. The tool description itself adds no parameter semantics beyond the schema, so the baseline score of 3 applies.

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 action ('Adds'), the object ('a sequence'), and the destination ('Adobe Media Encoder render queue'). This is specific and easily distinguishes from sibling tools like encode_file or start_batch_encode.

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 no guidance on when to use this tool versus related tools such as export_sequence, start_batch_encode, or encode_project_item. There are no example workflows, prerequisites, or alternative references, so an agent has no help choosing it over siblings.

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