MacRelay has 52 tools with consistent naming (verb_noun pattern) and basic descriptions, but critical gaps undermine quality. Most tools lack detailed input schemas, many show empty {} or missing parameter documentation. Descriptions are present but generic (avg ~60 chars, well below the 194-char baseline). No output schemas are documented. Error handling is absent, no recovery guidance, no categorization. Parameter descriptions are sparse or missing entirely. The smoke test file shows tool names and basic structure but does not reveal actual schema definitions or output documentation. This is a STDIO-only server with minimal schema rigor.

• Add complete JSON Schema input definitions for all 52 tools. For write/destructive tools (compose_message, create_event, etc.), document all required and optional fields with types, descriptions, and constraints (enums, min/max, patterns).
• Document output schemas for all tools. Specify field names, types, and structure.
• Expand tool descriptions to 100-200 chars. Include: what the tool does, when to use it vs similar tools, what it returns, and any prerequisites (e.g., 'Requires Contacts permission'). Follow pattern:tool-description.
• Add parameter descriptions to all inputs. For each parameter, state its type, valid values (enums), format (regex/length), and constraints. E.g., 'account (string): Mail account name; must match an account from communication_mail_list_accounts'.
• Implement error handling with recovery guidance. Categorize errors as retryable, user-fixable, or fatal. Return actionable messages: 'Note not found. Try productivity_notes_search_notes() first.' Follow pattern:recovery-guide.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry