Three tools with basic schemas and descriptions, but significant gaps in parameter documentation and error guidance. All tools are READ_ONLY and properly named with action verbs (search_*, play_*). Schemas are present but incomplete: search_music and search_album lack descriptions for the 'source' parameter; play_music has optional parameters but no guidance on mutual exclusivity (song_id vs songmid). Error handling returns structured responses but lacks recovery guidance. Output schemas are not documented. Descriptions are adequate (50-100 chars) but generic. No tool annotations (readOnlyHint, etc.) despite all being read-only. Average tool score: 52.

• Add explicit enum constraint for 'source' parameter: {type: 'string', enum: ['tx', 'wy', ''], description: 'Music source: tx (QQ Music), wy (NetEase), or empty string for default'}
• Document play_music parameter relationship: 'Exactly one of song_id or songmid must be provided. If both are given, song_id takes precedence.'
• Add output schema documentation to each tool. Example for search_music: 'Returns {ok: true, is_end: bool, data: [{id, songmid, title, artist, qualities}]} or {ok: false, error: string, message: string}'
• Enhance error messages with recovery hints. Example: 'Song not found. Verify song_id is numeric and source is valid (tx/wy).'
• Add readOnlyHint: true to all three tools in FastMCP registration to signal they are safe for retry and have no side effects