This server has 14 tools with basic schemas and descriptions, but quality is inconsistent. All tools have explicit input schemas with type information and parameter descriptions, which is good. However, descriptions are uniformly generic (12-50 chars) and lack LLM-optimized guidance on WHEN to use each tool or WHAT distinguishes similar tools. No tool descriptions include recovery hints, dependencies, or error guidance. Output schemas are completely undocumented, LLMs cannot determine what fields to expect from any tool. Tools like 'generate_statistics_report', 'generate_daily_brief', 'generate_weekly_report' are poorly differentiated, an LLM cannot easily decide which to call. Parameter descriptions are minimal (e.g., 'Number of days to analyze' with no range constraints). No tools declare error handling, retryability, or side effects. All tools are READ_ONLY, which is good for safety, but this is not explicitly stated in descriptions. The server lacks pagination guidance, output field documentation, and composition patterns.

• Document the output schema for every tool. Include field names, types (string, number, array, object), and what each field represents. Example: 'Returns {sleep_sessions: [{date, duration_hours, deep_sleep_minutes, efficiency_score}], total_nights: int}'.
• Expand tool descriptions from 1-2 sentences to 3-4 explicit sentences: (1) WHAT the tool returns, (2) WHEN to use it vs. similar tools, (3) ANY prerequisites or dependencies, (4) approximate response size if applicable.
• Add min/max constraints to all numeric parameters. 'days: integer, 1-365 (default: 30)' prevents invalid inputs and guides LLM reasoning.
• Replace free-form string parameters with enums where applicable. For 'training_type', enumerate: [running, cycling, strength, swimming, sports, recovery]. For 'metric1'/'metric2', enumerate valid metric names: [sleep_score, readiness_score, hrv, resting_hr, deep_sleep_duration, ...].
• Add error handling guidance to descriptions. E.g., 'If no data available for the requested date range, returns empty list. If API token expired, tool returns 401 Unauthorized, check server configuration.'
• Consolidate three report tools into two: 'generate_daily_health_report' (covers today) and 'generate_period_health_report' (covers days/weeks with date_start and date_end params). Document the distinction clearly.
• Document which tools return IDs or references that feed into other tools. If get_sleep_sessions returns sleep_session_ids, note that analyze_sleep_trend expects those IDs.
• Add pagination parameters (limit, offset) to tools that retrieve time-series or list data (get_sleep_sessions, get_heart_rate_data, get_raw_sleep_data). Document default limit and max limit (e.g., 'max 1000 records per call').