Kebab MCP exposes only 2 tools (vault_read, vault_write) with minimal schema documentation. Both tools have extremely brief descriptions (under 50 chars) that fail to explain WHEN to use them, WHAT they return, or dependencies. Input schemas are present but lack parameter descriptions, the 'path' and 'content' parameters have only type declarations, no guidance on format, constraints, or examples. No output schemas are documented. Error handling is absent, no recovery guidance, no validation rules, no actionable error messages. The tool names are verb-noun compliant but descriptions are far below the 50-200 char baseline for LLM-optimized tools. Risk annotations (READ_ONLY, WRITE) are present but not integrated into descriptions.

• Expand vault_read description to 80-150 chars: 'Read a file from your Obsidian vault by relative path. Returns file contents as plain text or markdown. Use this to retrieve notes, templates, or configuration files. Path must be relative to vault root (e.g., "folder/note.md").'
• Expand vault_write description to 100-150 chars: 'Write or overwrite a file in your Obsidian vault. Accepts plain text or markdown content. Creates parent directories if needed. Returns the file path and write timestamp. Use with caution, overwrites existing files without confirmation.'
• Add parameter descriptions: path → 'Relative path to file in vault (e.g., "folder/note.md"). Must not contain .. or absolute paths.'; content → 'File contents as plain text or markdown. Supports UTF-8 encoding.'
• Document output schemas: vault_read → {content: string, path: string, size: number, modified: ISO8601}; vault_write → {path: string, success: boolean, timestamp: ISO8601}
• Add error handling: 'If path not found, return error with available parent directories. If permission denied, return error with required vault permissions. If path traversal detected, reject with clear message.'