This server has critical gaps in parameter descriptions and output schema documentation. All 5 tools lack parameter descriptions (e.g., 'username' in username_to_uuid has no description beyond the type). No output schemas are documented anywhere. Tool descriptions are extremely terse (10-30 chars), below the 50-200 char baseline for LLM-optimized descriptions. The naming is reasonable (verb_noun pattern), but without parameter guidance and output specs, LLMs cannot reliably use these tools. Error handling is minimal, only HTTP status codes are checked, with generic error messages that don't guide recovery.

• Add 50-150 character descriptions to each tool explaining WHAT it does, WHEN to use it, and what it returns. E.g., 'Get the current UUID for a Minecraft username. Returns {id, name, legacy}. Use this to resolve a player name to their unique identifier before calling profile() or name_history().'
• Document all parameters with type, format, and constraints. E.g., 'username (string, 3-16 alphanumeric chars): The Minecraft username to look up. Case-insensitive.' and 'timestamp (number, optional): Unix epoch seconds. If omitted, returns current UUID.'
• Add output schema documentation for each tool. E.g., 'Returns {id: string (32-char hex UUID), name: string, legacy: boolean}' or 'Returns array of {changedToAt: number (epoch ms), changedTo: string, ...}'.
• Implement error classification: catch 404 as 'user not found, try a different username' (user-fixable), 429 as 'rate limited, retry in 60s' (retryable), 500 as 'Mojang API error, try again later' (transient).
• Add parameter validation with actionable errors. E.g., if uuid is not 32 hex chars, return 'Invalid UUID format: got "{uuid}", must be 32 hexadecimal characters (no dashes or braces).'