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. It only states 'Adds a sequence' without revealing side effects like whether rendering starts immediately, if overwrites are allowed, or if it blocks execution. Key behaviors implied by schema parameters (startImmediately, allowOverwrite, removeOnCompletion) are not mentioned, leaving the agent unaware of default behaviors.

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, clear sentence with no filler or redundancy. It is front-loaded and efficiently captures the core action without unnecessary details.

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?

Given the tool's complexity (8 parameters, integration with AME) and lack of output schema, the description is incomplete. It does not explain what happens after adding, how to monitor or cancel, or if there are dependencies on other tools. The minimal one-liner is insufficient for an agent to fully understand the operation's context and side effects.

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 8 parameters. The description adds no parameter-level meaning beyond the schema; it does not explain how parameters interact (e.g., presetName vs presetPath) or provide usage context. Baseline 3 is appropriate because the schema handles parameter rationale.

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 a sequence to the Adobe Media Encoder render queue.' It uses a specific verb and resource, distinguishing it from sibling tools like get_render_queue_status, export_sequence, or start_batch_encode by focusing on the queue addition.

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 guidance is provided on when to use this tool versus alternatives, such as export_sequence or encode_project_item. It does not mention prerequisites (e.g., having a sequence open, AME connection) or conditions for use, leaving the agent without context on choosing this over similar tools.

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