Server has 4 tools with schemas and descriptions, but quality is inconsistent. process_audio has a complex schema with 17 parameters but lacks output schema documentation. Descriptions are present but generic (10-50 chars for some params). No error handling guidance, no parameter validation rules, and no tool annotations. Parameter descriptions often omit constraints, ranges, and format expectations. The server lacks idempotency guidance for the write operation (process_audio). Overall structure is present but falls short of production-grade quality.

• Document output schemas for all tools. E.g., process_audio should return {file_path, duration, format, size_bytes, processing_time_ms}. preview_audio_params should return the resolved parameter object.
• Add min/max bounds to numeric parameters: speed (0.25 - 4.0), volume (0.0 - 3.0), normalize_level (-40 to 0 dB), lowpass/highpass (20 - 20000 Hz), fade_in/fade_out (0 - 60 seconds).
• Convert echo, chorus, flanger to enums: ['light', 'medium', 'heavy'] instead of free-form strings. Or provide FFmpeg filter parameter mappings in descriptions.
• Add error handling guidance: 'If audio file not found, call get_audio_metadata first to verify the file exists and is accessible. If processing fails with timeout, try reducing duration or increasing start_time.'
• For process_audio, document idempotency: 'This tool is NOT idempotent, calling twice with the same parameters will process the file twice. Use preview_audio_params to validate parameters before processing.'