Vault Bridge has well-structured tool definitions with complete input schemas and descriptions for all 6 tools. All tools follow verb_noun naming (read_note, write_note, list_notes, search_notes, search_frontmatter, get_daily_note). Descriptions are present and actionable (avg ~50 chars). However, output schemas are not documented in the source code, only input schemas are visible. Error handling returns ErrorResponse objects but lacks recovery guidance (e.g., 'try search_notes() first'). No tool annotations (readOnlyHint/destructiveHint) despite clear risk classifications. Parameter descriptions are adequate but some lack format constraints (e.g., date format for get_daily_note is mentioned in description but not enforced via schema pattern). The server creates fresh ObsidianCore instances per request (stateless), which is correct for 2026-07-28 spec.

• Document output schemas for all tools. Add Pydantic model definitions or JSON Schema examples showing returned fields (e.g., ReadNoteResponse with 'content', 'frontmatter', 'path' fields).
• Enhance error responses with recovery guidance. Instead of ErrorResponse(error='FileNotFoundError', message='...'), return ErrorResponse(error='FileNotFoundError', message='...', suggestion='Try list_notes(path="...") to discover available files.').
• Add tool annotations to FastMCP tool decorators. Use @mcp.tool(annotations={'readOnlyHint': True}) for read_note, list_notes, search_notes, search_frontmatter. Use destructiveHint=True for write_note and get_daily_note.
• Add pagination to list_notes and search_notes. Accept 'limit' (default 20, max 100) and 'offset' parameters. Return 'total_count' and 'has_more' in response so agents can iterate.
• Add JSON Schema format constraints. For get_daily_note, declare date parameter with format: 'date' and pattern: '^\d{4}-\d{2}-\d{2}$' to prevent invalid input.

Inferred effective spec: 2026-07-28+.

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