Extracts the audio track from a video or audio file and saves it as MP3, AAC, WAV, OGG, Opus, or FLAC, with the format determined by the output extension.
Extract the audio track to mp3, aac, wav, ogg, opus or flac (from the output extension).
| Name | Required | Description | Default |
|---|---|---|---|
| input | Yes | Path to the file (relative or absolute) | |
| format | No | Overrides the output extension | |
| output | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses that the output format is inferred from the output extension, but it does not explain overwrite behavior, error handling for files without audio, permissions, or what the tool returns.
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 a single front-loaded sentence with no wasted wording. The supported formats and format-inference rule are stated efficiently.
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?
For a three-parameter media tool with no annotations and no output schema, the description covers the core operation and format selection. It remains incomplete regarding return values, failure cases, and overwrite behavior.
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 67%, and the description adds useful meaning by clarifying that the output extension determines the format. The schema already documents the format override, so the description adds some but not comprehensive parameter context.
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 states a specific verb and resource: extract the audio track. It also lists the supported output formats, so the operation is clear. It does not explicitly distinguish itself from the sibling convert tool, which keeps it from a 5.
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 the tool is used to extract audio, but it gives no explicit when-to-use guidance. It does not mention alternatives such as convert, prerequisites, or when extraction is inappropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.