Server declares 10 tools with Zod schemas and basic descriptions. All tools have input schemas with type definitions and parameter descriptions, meeting minimum requirements. However, descriptions are uniformly terse (10-80 chars, well below the 194-char baseline), lack context on WHEN to use each tool, and omit dependency hints. No output schemas are documented. Tools 7-9 (analyze_performance, analyze_composition, get_improvement_tips) lack clarity on what 'AI recommendations' entails, are these LLM-generated or rule-based? Tool 10 (compare_players) lacks guidance on what comparison dimensions are returned. No error handling guidance, no recovery paths, no validation rules in descriptions. Parameter descriptions are minimal: 'Player name' and 'Tag line' don't explain format, length, or case sensitivity. Region parameter is optional across all tools but no default is stated. The server is transport-agnostic (UNKNOWN), which caps protocol readiness severely.

• Expand tool descriptions to 100-200 chars. Include WHEN to use (e.g., 'Call this first to get the player's PUUID, which is required for match history and live game checks'). Add dependency hints linking related tools.
• Document output schemas for all tools. Specify which fields are returned (e.g., get_account returns {puuid, summonerId, gameName, tagLine, region}). Ensure output includes IDs needed by downstream tools.
• Clarify analysis tools (7-9). State whether recommendations are LLM-generated or rule-based. Document the structure of returned suggestions (e.g., array of {category, suggestion, reasoning}).
• Add format constraints to parameter descriptions. E.g., 'gameName: Player name (1-16 chars, alphanumeric + spaces). tagLine: Tag suffix (1-5 chars, alphanumeric). region: Optional; defaults to na1 if omitted. Valid: euw1, na1, kr, br1, etc.'
• Add error handling guidance. E.g., 'If player not found, returns error with available similar names. If region is invalid, returns list of valid regions. All errors are retryable.'