add_to_render_queue

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the basic action. It does not mention whether rendering starts automatically, whether the queue persists, what happens with overwrite/removeOnCompletion, or that this is an asynchronous mutation of the render queue.

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 a single, direct sentence with no filler, and the action is front-loaded. It is concise, though for a tool with eight parameters and no annotations it is also quite sparse, so it does not earn a 5.

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 mutating, queue-manipulating operation with no output schema and no annotations, this description is incomplete. It does not explain what happens after the sequence is added, how to monitor the queue via get_render_queue_status, or how startImmediately and removeOnCompletion affect behavior, leaving an agent to infer crucial workflow context.

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 100%, so the schema already documents all eight parameters clearly. The description itself adds no parameter-level meaning beyond the schema, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Adds') and a clear resource ('sequence to the Adobe Media Encoder render queue'), so an agent can tell it involves queueing for AME. However, it does not explicitly distinguish it from related sibling tools like start_batch_encode, encode_project_item, or export_sequence, so it stops short of full differentiation.

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 instead of alternatives such as start_batch_encode, encode_project_item, or export_sequence. Nothing in the text indicates prerequisites, follow-up steps, or conditions that would make this the preferred choice.

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