queue_export

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the sequence is queued and rendered asynchronously in the background, but it omits prerequisites such as Adobe Media Encoder being available, the side effect of writing an output file, and what happens if startImmediately is false.

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 front-loaded sentence with no wasted text. The parenthetical adds useful behavioral context without bloating the definition.

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 five-parameter export tool with no annotations and no output schema, the description is too thin. It leaves out the required outputPath, the range enum behavior, startImmediately default, and what the caller receives after queueing.

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 20%, so the description should compensate for undocumented parameters. It mentions the sequence only as the resource being sent and does not explain outputPath, preset, range, or startImmediately semantics.

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 verb and resource: sending the sequence to Adobe Media Encoder's queue. The parenthetical clarifies the background-rendering behavior, but it does not explicitly distinguish this tool from siblings such as export_sequence or render_previews.

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 phrase 'renders in the background while you keep editing' implies when this tool is useful, but it does not explicitly say when to choose it over direct export alternatives. No exclusions or prerequisite conditions are provided.

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