Server has 4 tools with complete input schemas and descriptions. Naming follows verb_noun convention (list_, get_, current_). Descriptions are adequate (100-200 chars) but lack actionable context for LLM selection. Parameters have type definitions and descriptions, but lack enums for constrained inputs (league, season). Output schemas are not documented, LLMs cannot predict response structure. No error handling guidance. Missing pagination for list_leagues despite potentially large result sets.

• Add enum constraints for 'league' parameter: ['bl1', 'bl2', 'bl3', 'dfb', ...] with descriptions for each (e.g. 'bl1: Bundesliga (top tier)').
• Document output schemas in tool descriptions or as JSON Schema examples. E.g. 'Returns: {matches: [{id, matchday, datetime, team1, team2, finished, goals1, goals2, location}]}'.
• Add pagination to list_leagues: include 'limit' (default 50, max 100) and 'offset' parameters. Return total_count and next_offset in response.
• Enhance error messages with recovery guidance. E.g. if league not found, return 'Invalid league: "xyz". Valid leagues: bl1, bl2, bl3, dfb. Call list_leagues() for full list.'
• Add dependency hints to descriptions. E.g. get_matches: 'Call list_leagues() first to discover valid league codes and available seasons.'