obsidian-mcp demonstrates solid naming conventions (verb_noun pattern: vault_read, vault_write, vault_delete) and comprehensive tool coverage for Obsidian vault operations. However, critical gaps exist: 17 of 23 tools lack visible input schemas in the provided source code, making validation impossible. Descriptions vary widely, some tools (vault_create_folder, vault_reindex, vault_batch) have detailed, actionable descriptions (100-200 chars), while others (vault_read, vault_list, vault_write, vault_patch, vault_move, vault_delete, vault_links, vault_frontmatter, vault_search, vault_diff, vault_snapshot, vault_query, vault_read_multiple, vault_stats, vault_tags, vault_outline, vault_resolve_embeds, vault_obsidian_url) have no visible descriptions in the source. Output schemas are not documented. Error handling is present (errorReporting=true) but recovery guidance is not evident in the sample code.

• Add descriptions to all 17 undocumented tools. Each should state: WHAT it does, WHEN to use it (vs similar tools), and WHAT it returns. Target 50-200 chars per pattern:tool-description baseline.
• Document input schemas for all tools in TypeScript/JSON Schema. Include type, description, enum constraints, and min/max for numeric params. Verify against src/tools/*.ts files.
• Document output schemas for all tools. Specify returned fields, types, and which IDs/references are needed for downstream tool calls (e.g., vault_search must return file_path for vault_read).
• Add dry-run or confirmation step to vault_delete and vault_delete_folder. Return a confirmation_token that must be passed to execute the deletion, preventing accidental data loss.
• Enhance vault_batch error response to include per-operation status (success/failure/skipped) and rollback semantics. Document whether partial failures commit or roll back.