Server has 5 tools with basic descriptions and some parameter schemas, but significant gaps in schema completeness and parameter documentation. All tools are READ_ONLY and well-intentioned, but descriptions lack LLM-optimization guidance (e.g., when to use vs. similar tools). Parameter descriptions exist but are minimal. No output schemas documented. Error handling returns generic messages without recovery guidance. Naming is clear (verb_noun pattern), but composition could be tighter.

• Add input schema to get_next_match. Consider optional parameters like 'days_ahead' (1-30) to control search window, or 'include_details' (boolean) to control response verbosity.
• Document output schemas for all tools. Specify: for get_recent_matches, return array of {date, homeTeam, awayTeam, score, scorers[], venue, link}; for get_season_results, return {wins, draws, losses, goalsFor, goalsAgainst, matchSummaries[]}.
• Enhance error messages with recovery guidance. E.g., 'No matches found for competition "J2". Available: all, Qリーグ, なでしこリーグ, 皇后杯. Try a different competition or call get_recent_matches() without filter.'
• Expand tool descriptions to 100-150 chars. Add: 'Use this when you need [specific user intent]. Returns [data structure]. Differs from [similar tool] in that [distinction].'
• Add parameter descriptions explaining constraints and use cases. E.g., 'competition: Filter by league. "all" returns all competitions; specific league names reduce noise. Default "all" is recommended for discovery.'
• Consider splitting get_recent_matches into get_recent_matches (all competitions) and get_competition_matches (filtered), to reduce parameter confusion.

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

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