start_batch_encode

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds that this tool initiates encoding, confirming it is a mutation. However, it does not disclose potential side effects like whether the queue is cleared or if the operation can be stopped, which would add value beyond annotations.

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 sentence of 10 words that is clear, direct, and front-loaded with the key action. Every word earns its place, with no redundancy or filler.

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 simple parameterless mutation tool, the description adequately conveys its purpose. However, it lacks a brief note about when it is appropriate to invoke (e.g., after adding items to the queue) or what the result implies, which would make it slightly more complete.

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?

There are no parameters, and schema coverage is 100% by default. The description correctly adds no parameter information because none is needed. Baseline for 0 parameters is 4, and no additional meaning is required.

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 ('Start encoding') and the resource ('all items in the Adobe Media Encoder render queue'). It is specific and distinguishes from sibling tools like encode_project_item, encode_file, and add_to_render_queue by focusing on batch processing of queued items.

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 does not provide any guidance on when to use this tool versus alternatives, such as after adding items to the render queue. There is no mention of prerequisites, context, or explicit when-to-use/when-not-to-use information.

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