Server has 25 tools with consistent naming (verb_noun pattern) and descriptions in Korean. All tools have input schemas with type definitions and parameter descriptions. However, descriptions are often terse (many under 100 chars), output schemas are not formally documented, and error handling is generic ('success': false with error codes but limited recovery guidance). Tool composition is sound, tools are single-responsibility and chainable via IDs. Security is reasonable (no secrets in params, permission checks present). Naming is clear and action-oriented, but some parameter descriptions lack format/constraint details (e.g., date formats, enum values for 'span' and 'priority').

• Add formal JSON Schema output definitions for all tools. Document the 'success', 'error', 'message', and domain-specific fields (e.g., 'events', 'reminders', 'calendars') with types and descriptions.
• Convert parameter descriptions to explicit enums where applicable. Change 'span' description to list valid values: 'this_event | future_events'. Change 'priority' to 'none | low | medium | high'.
• Enhance error messages with recovery guidance. E.g., 'permission_denied: Calendar access not granted. Call eventkit_check_permissions to verify permissions, then grant access in System Preferences > Security & Privacy > Calendar.'
• Expand tool descriptions to 100-200 characters and clarify when to use each tool. E.g., 'calendar_search_events: Search by title, location, or notes across a date range. Use this when you know partial text; use calendar_list_events to retrieve all events in a date range.'
• Add pagination metadata to list responses: return 'total_count' and 'has_more' (boolean) so agents know if results are truncated and can paginate if needed.