The server has 14 tools with partial schema definitions visible in the tool registration files. Tool descriptions are present and moderately detailed (averaging 60-90 chars), exceeding the 20-char minimum but falling short of the production baseline of 194 chars. Parameter schemas are declared with types and descriptions for most tools, but output schemas are not documented in the source code provided. The logging wrapper adds value but does not compensate for missing output documentation. Most tools follow the verb_noun naming convention correctly (list_, get_, calculate_, analyze_, optimize_, suggest_). However, critical gaps remain: no per-tool error handling guidance visible, no idempotency hints or destructive operation safeguards for the admin_rebuild_cache tool, and incomplete parameter constraint documentation (e.g., the 'format' parameter accepts format codes like 'regf' and 'regg' but no enum or validation logic is shown in the source).

• Add documented output schemas for all 14 tools. Specify the exact JSON structure (field names, types, nested objects) that each tool returns. Use the pattern: 'Returns: { pokemon_id: string, name: string, usage_rate: number, ... }'
• Convert format parameter values to an enum in the input schema. Extract valid format codes (regf, regg, etc.) from the server's logic and declare them as enum: ['regf', 'regg', ...] in the schema for get_pokemon_usage, get_rankings, suggest_team_building, and get_pokemon_moveset.
• Implement error recovery guidance. Modify tool implementations to return structured errors with actionable messages: { error: 'Pokemon not found', available_pokemon: ['Pikachu', 'Charizard', ...], suggest_search: 'Call search_pokemon with a partial name' }
• Add a confirmation step or dry-run mode for admin_rebuild_cache. Include a 'dry_run' boolean parameter (default true) and update the description to explain the operation's impact: 'Rebuilds the internal Pokemon data cache. Use dry_run=false to confirm the operation; with dry_run=true (default), returns what would be rebuilt without making changes.'
• Expand EV and nature parameter descriptions. For calculate_stats, calculate_damage, and calculate_champions_stats, add format specification: 'EV spread as slash-separated values (e.g., "252/0/0/252/0/4") or JSON object {hp: 252, atk: 0, ...}. Total EVs must not exceed 510. Nature must be a valid Pokemon nature (e.g., "Timid", "Adamant").'
• Document pagination and limits. For tools returning multiple results (get_pokemon_usage, get_rankings, get_replay_analysis), add 'limit' (default 20, max 100) and 'offset' parameters. Return a 'total' field and 'has_more' flag in the response.

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

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