Three tools with clear verb-noun naming (search_tracks, get_lyrics, get_track) and good action-oriented descriptions. All tools have input schemas with typed parameters and descriptions. Tool descriptions range 66-179 chars, within the 10-1024 baseline. However, parameter descriptions are sparse and domain-specific context could be stronger. All tools correctly marked as read-only with proper hints. Output schemas are documented but not exposed in schema definitions themselves. No critical security issues (read-only, no credentials). Main gaps: parameter descriptions could be more detailed (format, constraints, examples), output structure not formally specified in schema, and pagination/result limits not addressed despite potential for large result sets.

• Add detailed parameter descriptions for all inputs: e.g. 'id (number): LRCLIB numeric track identifier (obtain from search_tracks result)' or 'syncedLyrics (boolean, default=false): Return time-synced LRC format if available; false returns plain lyrics.'
• Document search_tracks parameter logic: 'Free-text query (q) and structured fields (trackName, artistName, albumName) can be combined with AND logic. Omit fields to search only on provided criteria.'
• Add output schema documentation to tool descriptions. E.g. 'Returns: { tracks: [{ id, name, artist, album, duration_ms }], total_count, limit }' so LLM knows what fields are available for downstream use.
• Implement and document pagination: 'Results are limited to 20 tracks per call. Use offset parameter to paginate through large result sets.' Include offset/limit in searchTracks input schema.
• Add error recovery guidance: 'If track_id is not found, returns null or error. Call search_tracks to locate track by metadata. If LRCLIB API is unavailable, returns timeout error, safe to retry after 30s.'
• Constrain search query: Add max length (e.g. 255 chars) and valid character guidance to 'q' parameter description. Note: searches are case-insensitive and strip punctuation.
• Document syncedLyrics default and behavior: 'If true and LRC lyrics exist, prioritize synced format; otherwise return plain. If false, always return plain text lyrics.'
• Add usage flow in server instructions: Already present but could link from individual tool descriptions for discoverability.

Inferred effective spec: 2025-06-18+.

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