Server has 6 tools with critical definition gaps. Five tools (get_cfb_news, get_nfl_news, get_mlb_news, get_nhl_news, get_nba_news) have empty input schemas {} with no parameters documented, violating the constrained-input pattern. Descriptions are present but generic (10-50 chars), below the 50-200 char baseline for LLM-optimized tools. get_nhl_team_info accepts a 'team' parameter but the implementation ignores it (hardcoded 'toronto'), creating a broken tool contract. No output schemas documented. Error handling returns generic strings without recovery guidance. Tool names follow verb_noun convention (positive), but lack specificity about what data is returned.

• Add explicit input schemas to all tools. For news tools, add optional 'limit' (1-50, default 20) and 'offset' (0+, default 0) parameters to support pagination and prevent context window exhaustion.
• Fix get_nhl_team_info: use the 'team' parameter in the URL instead of hardcoding 'toronto'. Validate team name against known NHL teams or return a helpful error with available options.
• Expand descriptions to 50-200 chars. Example: 'Get the latest news articles for college football (NCAA). Returns up to 20 articles with headline, description, and link. Call this to stay updated on CFB news.' Include WHEN to use and what to expect.
• Document output schemas. Define that news tools return an array of objects with fields: type (string), headline (string), description (string), link (string). Include this in tool descriptions or as a separate schema reference.
• Improve error messages with recovery guidance. Instead of 'Unable to fetch articles', return 'ESPN API unavailable. Retry in 30 seconds, or check your internet connection.' For invalid team names, return 'Team not found. Available NHL teams: Toronto, Montreal, Boston, ...'.