Start Batch Encode

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

The annotations are all false/default and provide little safety context, so the description carries the disclosure burden. It only names the action and target, omitting whether encoding starts asynchronously, whether the queue is cleared, or what side effects occur.

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?

A single 11-word sentence that states the action and the target with no filler. It is front-loaded and every word contributes.

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 zero-parameter action with an output schema, the description is minimally viable, but it omits practical context: it does not mention prerequisites (items must already be in the render queue) or the natural follow-up (e.g., checking status with get_render_queue_status).

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 tool has zero parameters and the schema fully covers this by having an empty properties object. The description adds the useful scoping detail 'all items', which is sufficient; no parameter-level clarification is needed.

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 ('Start encoding') and a precise resource ('all items in the Adobe Media Encoder render queue'), making the tool's action unambiguous and distinct from single-item encode siblings like encode_project_item or encode_file.

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 about when to use this tool versus alternatives. The description does not mention that this is the batch option, nor does it route to single-item or status-checking tools such as encode_project_item or get_render_queue_status.

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