video_generate_subtitles

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

No annotations are provided, so the description carries full burden. It discloses that burn=True modifies the video, but does not explain whether subtitles are saved as a separate file, overwrite existing subtitles, or require any permissions. Key behavioral traits like output location and side effects are missing.

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 short and structured with an Args list. It front-loads the main purpose. While the Args list repeats schema info, it adds type clarity. Overall efficient and readable.

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 (3 params, 2 required, no nested objects, output schema present), the description does not mention return values or what happens after execution (e.g., modified video, separate SRT file). It lacks completeness about the tool's effect on files.

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 schema has 0% description coverage. The description adds meaning by specifying the keys of entries (start, end, text) and their types (float, str). However, it does not explain the time format (e.g., seconds or milliseconds) or constraints on input_path, leaving some ambiguity.

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 tool generates SRT subtitles from text entries and optionally burns into video. It specifies the resource (SRT subtitles) and action (generate). However, it does not differentiate from sibling tools like video_subtitles or video_subtitles_styled, which could be confused.

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 such as video_subtitles or audio options. It does not mention prerequisites, preferred scenarios, or when not to use it.

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