transcribe_video

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

Discloses that it downloads/extracts audio and uses whisper.cpp, but no annotations provided. Missing information on file size implications, time costs, or whether it overwrites existing files. Moderate transparency.

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?

Very concise two sentences, front-loaded with core function. Every sentence provides essential information without redundancy.

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 main functionality but lacks details on output structure, error handling, and prerequisites. Given no output schema and no annotations, description is moderately complete.

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; description adds speed and format details but does not explain parameter-specific behavior beyond schema. Baseline is adequate.

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 it transcribes videos from a wide range of platforms and local files. Uses specific verb 'Transcribe' and describes output formats. Distinguishes from sibling tools like delete/list.

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?

No explicit guidance on when to use this tool vs alternatives. Does not mention when not to use or provide context for selection among siblings. The description mentions speed advantage but lacks clear usage directives.

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