Replace a video's audio track with a new audio file. The output duration matches the shorter of the two inputs.
Swap a video's audio track with another audio file. Output ends when the shortest input ends.
| Name | Required | Description | Default |
|---|---|---|---|
| audio_path | Yes | Local path to the new audio file | |
| video_path | Yes | Local path to the video |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds a meaningful behavioral detail: output ends when the shortest input ends. However, with no annotations, it does not disclose whether the original video is overwritten, where the output file is written, or how audio encoding is handled.
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 short sentences with no filler. The core purpose is front-loaded, and the behavioral constraint is stated efficiently in the second sentence.
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 two-parameter tool this is reasonably usable, but the lack of annotations and output schema leaves an agent uncertain about the return value and output file behavior. The description should at least indicate whether a new file is produced or the source is modified.
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 already fully describes both parameters with clear one-line descriptions, so the description adds no additional per-parameter meaning. Baseline 3 is appropriate given 100% schema coverage.
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?
States a specific verb and resource: swapping a video's audio track with another audio file. This clearly distinguishes it from sibling tools like extract_audio, adjust_volume, and trim_video.
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 guidance is given about when to use this tool versus alternatives such as adjust_volume or extract_audio, and no prerequisites or exclusions are mentioned. The usage context must be inferred entirely from the description and tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.