Metrone MCP exposes 7 analytics tools with basic schemas and descriptions. All tools have names starting with action verbs (get_, track_) and descriptions present. However, most parameter descriptions are minimal (under 50 chars), many lack type constraints (enums, ranges), and output schemas are not documented. Error handling is absent, no recovery guidance or actionable error messages. The tool set is well-composed (read-only queries + write tracking), but parameter documentation falls short of production standards. No tool annotations (readOnlyHint/destructiveHint) despite clear risk classification.

• Add enum constraints to 'event_type' and 'source' parameters. Document valid values explicitly (e.g., source: enum ['voice', 'chat', 'assistant', 'web', 'api']).
• Document numeric ranges: 'days' (1 - 365), 'limit' (1 - 100), 'duration' (0 - 86400). Add these to parameter descriptions so LLMs know valid bounds.
• Define output schemas for all tools. Specify field names, types, and whether results are paginated. Example: 'Returns {events: [{id, type, timestamp, properties}], total: number, hasMore: boolean}'.
• Add tool annotations: readOnlyHint=true for all get_* tools; destructiveHint=true for track_* tools. This signals to agents which calls are safe to retry.
• Implement error handling with actionable messages. Return structured errors: {error: 'invalid_days', message: 'days must be 1 - 365', suggestion: 'Try days=30'}. This enables agent self-correction.