Start Batch Encode

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

The annotations already state readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the description does not need to repeat safety basics. It adds useful behavioral context by clarifying the asynchronous, handoff-only nature of the call and explicitly bounding what the response does not represent.

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 efficient sentence with the action front-loaded followed immediately by the important limitation. Every clause earns its place by clarifying scope and avoiding false expectations.

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 zero parameters, available annotations, and an output schema, the description is complete enough for an agent to invoke the tool correctly. It states the action and the key behavioral boundary without needing to explain return values.

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, so there are no parameter semantics for the description to explain. The baseline for a zero-parameter tool with an empty input schema is 4.

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: request Adobe Media Encoder to start the render queue. It also distinguishes the tool's scope from related operations by clarifying that it only reports an accepted handoff and does not report queue progress or output-file creation.

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?

It gives clear context for when to use the tool and explicitly excludes expectations of progress or output-file creation. However, it does not name the alternative sibling tools for checking progress or confirming completed output, leaving that inference to the agent.

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