start_batch_encode

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

No annotations are present, and the description does not disclose any behavioral traits such as whether the operation is asynchronous, what side effects occur, whether it blocks, or what output to expect. It only restates the tool name.

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 extremely short, but the prefix 'Premier Pro expanded operation:' is filler and does not earn its place. The core 'start batch encode' is concise, but the additional phrase does not improve clarity.

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 complexity of encode operations, the tool has no output schema, no annotations, and no parameter definitions, leaving the agent completely in the dark about what inputs are accepted, what action is performed, and what is returned. This is entirely inadequate.

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 defined parameters, so the schema provides no meaningful information. Per the rubric, a baseline of 4 is appropriate for zero-param tools; the description does not need to explain parameter syntax, though it could mention that no parameters are 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 says 'start batch encode,' which gives a clear verb and resource, but it does not specify what 'batch' refers to or how it differs from sibling encode tools. The phrase 'Premier Pro expanded operation' is vague and adds no real meaning.

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 provides no guidance on when to use this tool versus alternatives like encode_project_item, encode_file, or add_to_render_queue. There are no examples, no context, and no exclusions.

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