Server has 4 tools with basic schemas and descriptions, but significant gaps limit production readiness. All tools have descriptions (good), but descriptions are verbose and contain implementation details rather than LLM-optimized guidance. Schemas are present but lack proper type annotations in the visible code, parameters use union types and nullable fields inconsistently. get_tournaments has a 600+ char description mixing API docs with agent instructions, violating the 10-1024 char guideline. No output schemas documented. Error handling returns raw error strings without recovery guidance. Tool names follow verb_noun pattern (good), but parameter naming is inconsistent (game vs organizerId mixing conventions).

• Refactor get_tournaments description from 600+ chars to ~100 chars: 'Retrieve tournaments with optional filtering by game, format, organizer, limit, and page. Defaults to VGC. Returns paginated list.' Move agent instructions (fuzzy matching, pagination logic) to server.instructions.
• Document output schemas for all 4 tools. Example for get_tournaments: {type: 'object', properties: {tournaments: {type: 'array', items: {type: 'object', properties: {id, name, game, format, date}}}, total: {type: 'number'}, page: {type: 'number'}}}
• Standardize parameter naming to snake_case: rename 'organizerId' → 'organizer_id'. Ensures consistency with response field naming and reduces LLM confusion.
• Replace raw error strings with actionable recovery guidance. Example: 'Tournament not found. Try searching with a partial name using get_tournaments(game="VGC", limit=50) to browse available tournaments.'
• Move Pokemon restricted list and nickname mappings from get_tournament_standings description to a separate resource or server.instructions. Keep tool description under 150 chars.