Server has 8 well-named tools with clear verb-noun patterns (list_notes, read_note, search_notes, etc.). All tools have descriptions and input schemas with typed parameters. However, descriptions are terse (10-50 chars), parameter descriptions lack detail on constraints/formats, output schemas are undocumented, and error handling lacks recovery guidance. No tool annotations (readOnlyHint, destructiveHint) despite clear risk stratification. Missing pagination for list_notes and search_notes despite potentially large result sets.

• Expand tool descriptions to 150-250 chars. Include WHAT (action), WHEN (use case vs similar tools), and WHAT IT RETURNS (structure hint). E.g., 'List all notes in a folder (optionally recursive). Returns array of {path, name, modified_time}. Use this to discover available notes before read_note or search_notes.'
• Document output schemas for all tools. Define return types as JSON Schema or prose. E.g., list_notes returns {notes: [{path: string, name: string, size: number}], total: number}.
• Add tool annotations: readOnlyHint=true for list_notes/read_note/search_notes/get_note_metadata; destructiveHint=true for delete_note; idempotentHint=true for write_note (with overwrite=true).
• Add pagination to list_notes and search_notes: limit (1-100, default 20), offset (default 0), and return total_count. Document in description: 'Results capped at 100 per call; use offset for pagination.'
• Enhance parameter descriptions with constraints: folder='vault-relative path, empty string for root'; mode='enum: filename|content'; overwrite='default false; if true, replaces existing note'.