Server has 8 tools with explicit schemas and descriptions, but quality is inconsistent. All tools have basic descriptions (10-50 chars), which is below the 50-200 char baseline for LLM-optimized descriptions. Parameter descriptions are minimal or missing context. No output schemas documented. Error handling is generic ('Tool execution failed') with no recovery guidance. Tool names lack action verbs (e.g., 'courses' instead of 'list_courses', 'materials' instead of 'get_materials'). No parameter validation, no enum constraints, no field-level documentation. The 'download' tool accepts a URL parameter but provides no format constraints or validation hints.

• Rename tools to verb_noun pattern: list_courses, get_grades, list_assignments, get_materials, list_deadlines, get_announcements, download_file, get_summary.
• Expand descriptions to 50-200 chars with WHAT, WHEN, and EXPECTED OUTPUT. E.g., 'List all enrolled courses with IDs, names, and enrollment status. Call this first to discover available courses before querying grades or assignments.'
• Document output schemas for each tool. E.g., courses returns [{course_id: int, course_name: str, enrollment_date: ISO8601, status: str}]. This enables LLM planning.
• Replace generic error handling with categorized, actionable messages. E.g., 'Course not found (ID: 123). Available courses: [list]. Try list_courses() to discover valid IDs.' or 'Authentication failed. Check config.json and MOODLE_CRED_PASSWORD environment variable.'
• Add parameter constraints: course_id as positive integer, url as valid HTTP(S) URL with format validation, output as valid file path. Use enums for status/filter fields if applicable.