Server has 8 tools with complete input schemas and descriptions present. However, descriptions are generic and lack LLM-optimization guidance (e.g., 'Get full details' vs 'Retrieve problem statement, constraints, examples, and test cases to understand the problem before coding'). Parameter descriptions are minimal or absent. No output schemas documented. Error handling is basic. Tools lack actionable recovery guidance. Naming is clear (verb_noun pattern) but descriptions don't explain WHEN to use each tool or dependencies between them.

• Document output schemas for all tools. E.g., list_problems should return {problems: [{id, title, difficulty, category, solved}], total_count, has_more}. Include field types and descriptions.
• Enhance descriptions with WHEN-to-use guidance and dependencies. E.g., 'Call list_problems first to discover available problems, then get_problem to fetch full details before coding.'
• Add parameter descriptions explaining format, constraints, and how to obtain values. E.g., 'id: Problem identifier in format NNNN-slug (e.g., 0001-two-sum). Obtain from list_problems or search_problems results.'
• Implement actionable error messages. E.g., if auth is missing, return 'Authentication required. Run: ./start-leetcode --setup-auth' instead of generic error.
• Add pagination to list_problems and search_problems with limit (1-100, default 20) and offset parameters. Return total_count and has_more flag to enable LLM-driven pagination.