Three tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. Tool names follow verb_noun convention (extract_frames, get_media_info, transcode_push), which is good. However, descriptions lack actionable context for LLM selection, parameters are under-documented (missing descriptions for optional params in transcode_push), and output schemas are not formally documented. No error handling guidance, no enum constraints on codec/format parameters, and no indication of which operations are destructive. The server uses mcp-go framework correctly but definitions fall short of production quality.

• Add descriptions to all optional parameters in transcode_push. Example: 'codec_video: Video codec name (e.g., libx264, libx265, copy). Defaults to copy (no re-encoding).'
• Declare codec_video, codec_audio, and format as enums with valid options. Example: codec_video enum: [libx264, libx265, copy, mpeg2video, vp9].
• Document output schemas for each tool. Example for get_media_info: 'Returns {filename, duration, streams: [{index, codec_type, codec_name, width, height, ...}], frames: [{stream_index, pts, pict_type, ...}]}'.
• Add destructive operation hints to tool descriptions. Example: 'extract_frames: Extracts frames from a video file and WRITES output files to disk. Creates output directory if needed.'
• Enhance error messages with recovery guidance. Example: 'ffmpeg execution failed: invalid input file. Verify the file exists and is a supported format (mp4, mkv, avi, mov, etc.).' or 'Output directory creation failed: permission denied. Check write permissions on the parent directory.'