video_batch

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

No annotations are provided, and the description only outlines parameters without disclosing behavior such as error handling, partial failures, or concurrency for batch processing.

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 concise and front-loaded with the main purpose. The list of operations is clearly formatted, though truncated slightly in the provided text.

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?

The description covers basic usage for a batch tool, but lacks details on output format, error behavior, and potential limitations. Since an output schema exists, the return values are partially addressed, but not fully.

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 0%, but the description gives basic semantics for each parameter (e.g., inputs as absolute paths, operation list, params as parameters, output_dir auto-generated). However, it lacks detail on the structure of 'params'.

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 'Apply the same operation to multiple video files' with a specific list of operations, distinguishing it from siblings that operate on single files.

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 implies batch use but does not explicitly state when to use this tool vs. single-file tools like video_trim or video_resize, nor does it mention alternatives.

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