All 5 tools have basic descriptions and input schemas, but quality is inconsistent. Descriptions are adequate (50-150 chars) but lack actionable context for LLM selection. Parameter descriptions exist but are generic ('The unique identifier of the website' repeated 4 times). No output schemas documented. No error recovery guidance. No tool annotations (readOnlyHint present in metadata but not in schema). Tools are read-only, which is good, but descriptions don't explain WHEN to use each tool vs. alternatives (e.g., when to call get_stats vs get_metrics). Parameter constraints (e.g., date format, metric_type enum values) are mentioned in descriptions but not formalized in schema. No pagination support despite analytics tools typically returning large datasets.

• Document output schemas for all tools. Example: get_websites returns {websites: [{id: string, name: string, domain: string}]}. Include field types and descriptions so LLMs know what to extract.
• Add enum constraints to schema for metric_type (url, referrer, browser, country, etc.) and unit (day, week, month, year). Replace description examples with formal schema constraints.
• Clarify website_id format in parameter descriptions. Is it a UUID, numeric ID, or slug? Provide an example: 'Website ID (UUID format, e.g., 550e8400-e29b-41d4-a716-446655440000)'.
• Add pagination to get_pageviews and get_metrics: include limit (default 20, max 100) and offset parameters. Return total_count in response so LLM knows if more results exist.
• Enhance error messages with recovery guidance. Example: 'Website not found (ID: abc123). Call get_websites() to list available websites.' instead of 'Failed to get stats: website not found'.