Apple Notes MCP demonstrates solid tool design with consistent naming (verb_noun pattern), comprehensive parameter descriptions, and proper Zod schema validation. All 10 tools have clear descriptions (avg ~120 chars) and well-documented parameters. Tool annotations (readOnlyHint, destructiveHint) are correctly applied. However, output schemas are not explicitly documented, responses are JSON-serialized but lack formal schema declarations. Error handling is minimal; no recovery guidance or actionable error messages visible in the code. Some parameter relationships (e.g., noteId vs title lookup fallback) could be more explicit. Dry-run patterns on destructive operations (notes_delete, notes_move) are excellent for safety.

• Add formal output schema documentation to each tool. Define the structure of the JSON response (e.g., notes_search returns {notes: [{id, title, plaintext?, html?, ...}], total: number}). This enables LLMs to plan multi-step workflows.
• Implement comprehensive error handling with actionable messages. Example: 'Note not found with title "Meeting Notes" in folder "Work". Try notes_search() to find the correct note ID.' Catch AppleScript failures and return structured error objects with recovery hints.
• Explicitly document parameter relationships in descriptions. For notes_get, add: 'Either provide noteId (preferred) OR title + optional accountName/folderName. If both are provided, noteId takes precedence.'
• Add pagination support to notes_search. Introduce offset/cursor parameter and return a next_cursor field in results. Document the limit default (25) and max (200) in the description.
• Implement a multi-round-trip confirmation pattern for destructive operations. When dryRun=false on notes_delete or notes_move, return a confirmation request (MCP result type 'input_required') asking the user to approve before executing.