generate-subtitles

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

Describes the engines (OpenAI Whisper, local whisper) and output formats, but does not disclose potential side effects (e.g., file creation, processing time, API key requirements for some engines). With no annotations, it partially covers behavioral traits but could be more explicit.

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?

Two sentences, 20 words, no filler. Front-loaded with the core purpose and key details. Every word earns its place.

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?

Covers the main functionality and output, but lacks mention of return value (e.g., actual path to created subtitle file) and prerequisites. For a 4-parameter tool with high schema coverage, it's mostly complete but has minor gaps.

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 has 100% coverage with clear descriptions; the description adds value by noting that the subtitle file is created 'alongside the video', which is not in the schema. This extra context enhances parameter understanding.

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?

Clearly states the tool generates subtitles for a local video file using AI speech-to-text, specifying the output format (SRT or VTT) and placement (alongside video). Distinguishes from siblings like 'transcribe-audio' which produces transcripts, not subtitle 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?

Implies usage when subtitles are needed, but lacks explicit guidance on when to use this tool versus alternatives like 'transcribe-audio' or 'get-transcript'. Does not mention prerequisites (e.g., video file existence, API key for OpenAI engine).

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