Transcribe a MEGA video/audio file

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

With no annotations, the description carries full burden. It discloses that the tool is disabled by default, requires backend configuration, downloads the file, extracts/segments audio with ffmpeg, and sends to backend. This is good transparency, though it omits rate limits or response format.

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 (4 sentences) and front-loaded with purpose. Each sentence adds information without fluff, though it could be slightly more structured (e.g., grouping prerequisites).

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 5 parameters and no output schema, the description explains the process and prerequisites but does not specify the output format (beyond 'to text') or whether results are returned directly. Somewhat incomplete.

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 coverage is 100%, so baseline is 3. The description adds specific context for maxMinutes ('transcribe only the start of a long file'), but other parameters are already well-described in the schema. The added value is minimal.

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 verb ('Transcribe') and resource ('spoken audio from a video/audio file'), and this purpose is distinct from sibling tools (e.g., mega_browse, mega_read_file) which are not transcription-related.

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 mentions the OPT-IN requirement and provides a usage hint for maxMinutes, but it does not explicitly compare to alternatives or state when to use this tool vs. others. The sibling tools are unrelated, so context is implied.

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