Both tools have minimal descriptions and critically lack input parameter schemas. get_piano_roll_state has an empty input schema ({}), violating the requirement that every parameter needs a description and type. send_notes has a schema with parameter descriptions, but the descriptions are embedded in a single 'notes' parameter rather than individual parameter definitions. Neither tool documents output schemas. Descriptions are present but generic (10-50 chars), below the 50-200 char baseline for LLM-optimized tools. No error handling guidance, no recovery paths, no validation rules documented.

• Expand get_piano_roll_state description to 100-150 chars: 'Reads the current piano roll state from FL Studio. Requires the FL Studio script to have exported state via the Export State button. Returns JSON with note list, tempo, time signature, and track metadata. Call this first to inspect current state before sending notes.'
• Refactor send_notes schema: define 'notes' as array of objects with individual typed fields (midi: integer 0-127, duration: number >0, time: number >=0, velocity: number 0.0-1.0). Add 'mode' as a separate enum parameter with values ['add', 'replace'].
• Document output schemas: get_piano_roll_state should return {notes: [{midi, duration, time, velocity}], tempo: number, time_signature: string}. send_notes should return {success: boolean, notes_added: integer, error?: string}.
• Add error handling: 'If the exported JSON file is not found, ensure FL Studio script has run Export State. If FL Studio is not running, call focus_fl_studio first. If notes are invalid (MIDI out of range, negative duration), the tool returns an error with the invalid field and constraint.'
• Add parameter constraints to descriptions: 'midi (0-127, MIDI note number)', 'duration (positive number, multiplier of quarter notes)', 'velocity (0.0-1.0, where 0.8 is default)'.