FramePro MCP has 4 tools with clear verb-noun naming (analyze_*, find_*, compare_*) and reasonable descriptions (100-150 chars). However, critical gaps undermine quality: parameter descriptions are minimal or absent (e.g., 'focus' lacks enum values; 'top_n' has no range), output schemas are undocumented (tools return JSON but structure is not declared), and error handling is generic ('Failed to load FramePro data' with no recovery guidance). No tool annotations (readOnlyHint, idempotentHint) despite all being read-only. Parameter validation is weak, 'focus' accepts free-form strings instead of enum constraints. Baseline: 549 production tools average 194 chars for descriptions and 100% have documented return types; this server has neither.

• Add enum constraint to 'focus' parameter: mcp.WithEnum('focus', 'cpu', 'memory', 'frames', 'threads', 'all') with description 'Focus area for analysis (default: all)'.
• Document output schema for each tool. E.g., analyze_performance returns {file, focus, issuesFound, issues: [{severity, category, description, impact, suggestion, value}], summary}. Include this in tool description or as a separate schema field.
• Add range constraints to numeric parameters: top_n (1 - 100, default 10), target_fps (1 - 240, default 60). Update descriptions to state these bounds.
• Enhance error messages with recovery guidance. E.g., 'File not found: /path/to/file.json. Ensure the file exists and is valid FramePro JSON. Check FRAMEPRO_DATA_DIR environment variable.'
• Add tool annotations via mcp-go API (if supported): mark all tools with readOnlyHint=true to signal they are safe to call without user confirmation.