Video & Audio Editing MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'attempting to copy the video stream' which hints at preservation behavior, but doesn't address critical aspects like whether this is a destructive operation, what happens if the bitrate change fails, performance characteristics, or file format limitations. This leaves significant gaps for a mutation tool.

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 well-structured with purpose statement, Args section, and Returns section. Every sentence adds value, though the 'attempting to copy the video stream' phrase could be more precise. It's appropriately sized for a 3-parameter tool without unnecessary elaboration.

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 mutation tool with no annotations and no output schema, the description covers parameters well but lacks sufficient behavioral context. It doesn't explain what 'success or failure' entails, error conditions, or the preservation guarantee for the video stream. Given the complexity of video processing, more detail about limitations and outcomes would be beneficial.

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?

With 0% schema description coverage (titles only provide parameter names), the description fully compensates by clearly explaining all three parameters: input_video_path ('Path to the source video file'), output_video_path ('Path to save the video with the new audio bitrate'), and audio_bitrate ('Target audio bitrate' with example format '128k', '192k'). This adds essential meaning beyond the bare schema.

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 specific action ('Sets the audio bitrate of a video's audio track') and resource ('video's audio track'), with the additional detail 'attempting to copy the video stream' that distinguishes it from sibling tools like 'set_audio_bitrate' which likely processes audio files directly. This provides precise differentiation.

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 usage when modifying audio bitrate while preserving video, but doesn't explicitly state when to use this tool versus alternatives like 'set_audio_bitrate' or 'convert_video_properties'. No exclusions or prerequisites are mentioned, leaving usage context somewhat inferred rather than clearly defined.

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