Critical gaps across naming, descriptions, and schemas. Only 25 tools listed but server.py imports 70+ modules, suggesting massive undocumented tool inflation. Visible tools (fl_list_midi_ports, fl_connect, fl_get_status, etc.) have basic descriptions (10-50 chars) far below the 194-char baseline. No input schemas visible for any tool except fl_insert_notes (partial). Parameter descriptions are minimal or absent. No output schemas documented. Error handling guidance missing. This server prioritizes breadth over quality.

• Document output schemas for all list/query tools (fl_get_status, fl_list_channels, fl_list_patterns, fl_list_installed_plugins, fl_list_library). Include field names, types, and example values so LLMs can extract and chain data.
• Expand tool descriptions to 100 - 200 chars. Add WHEN to use, prerequisites, and error recovery hints. Example: 'fl_play: Start playback. Call fl_get_status first to verify connection. If playback doesn't start, check that FL Studio is running and a MIDI port is connected via fl_connect.'
• Add parameter validation rules to descriptions. For fl_set_tempo, state 'BPM must be 1 - 300'. For fl_set_channel_volume and fl_set_channel_pan, state 'volume/pan must be 0 - 127'. For fl_insert_notes, state 'pitch: 0 - 127 or note name (C4, F#3, Bb4); velocity: 0 - 127; duration: 1 - 10000 ticks'.
• Audit and document the 70+ imported tool modules (composition, vision, stems, etc.). Either remove unused modules or provide full schemas, descriptions, and parameter documentation for each. Currently they are dead code or undocumented.
• Add error classification and recovery guidance. For tools that can fail (fl_connect, fl_load_plugin, fl_load_file), document: 'If port not found, call fl_list_midi_ports to see available ports.' 'If plugin not found, call fl_list_installed_plugins to verify the name.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry