Four tools with basic verb-noun naming (get_*, delete_*). All have descriptions (10-80 chars, below baseline 194 avg). Input schemas present with type and description for all params. Critical gaps: no output schemas documented, no error recovery guidance, no pagination for list tools, delete_note lacks confirmation/dry-run pattern, descriptions are terse (under 50 chars each), no parameter constraints (enums, ranges), no mention of prerequisites or when to use each tool. Tool composition is reasonable but output handling is unstructured (returns plain strings, not JSON objects).

• Document output schemas as JSON objects. E.g., get_list_of_notes should return {notes: [{title: string, updated: string}], total: number} instead of plain text.
• Expand descriptions to 100-200 chars. Include WHEN to use: 'Get the N most recently updated notes. Use this to browse recent work; use get_notes_by_tag to filter by topic.'
• Add bounds to number_of_notes (1-100) and implement pagination (limit, offset params) with total count in response.
• Add confirmation step to delete_note: return {status: 'confirm_required', note_title, message: 'Delete note X? This cannot be undone.'} and require a separate confirm_delete_note tool.
• Enhance error messages with recovery hints: 'Bear database not found at ~/Library/Group Containers/... Ensure Bear is installed and running on macOS.'