13 tools with complete schemas and descriptions, but descriptions are terse (avg 50 chars, well below 194-char baseline). All tools have input schemas with proper types. Naming follows verb_noun pattern consistently (obsidian_list, obsidian_navigate, etc.). No parameter descriptions beyond the schema, LLMs must infer meaning from names alone. Output schemas undocumented. Error handling minimal (no recovery guidance, no categorization). No tool annotations (readOnlyHint/destructiveHint). Risk metadata present but not integrated into descriptions.

• Expand tool descriptions to 100 - 200 chars. Include WHAT (action), WHEN (use case), and WHAT IT RETURNS. E.g., 'Evaluate JavaScript code in the context of a Web viewer tab and return the result. Use this to extract data, trigger events, or inspect DOM state. Returns the evaluated expression result as JSON.'
• Document output schemas for all tools. E.g., obsidian_read_text returns {text: string, length: number, truncated: boolean}. obsidian_screenshot returns {data: string (base64), format: string, size: number}.
• Add tool annotations via MCP. Mark obsidian_list_tabs, obsidian_read_state, obsidian_read_text, obsidian_screenshot, obsidian_query_selector with readOnlyHint=true. Mark obsidian_new_tab, obsidian_navigate, obsidian_click, obsidian_type, obsidian_press_key, obsidian_scroll, obsidian_focus with destructiveHint=true.
• Enhance error messages with recovery guidance. E.g., 'No Web viewer tab matched: "xyz". Available tabs: [list]. Call obsidian_new_tab(url) to open a new tab, or use obsidian_list_tabs() to see all open tabs.'
• Clarify the 'tab' parameter in all 11 tools that use it. Document: 'Tab specifier: number (0-based index), string (URL or title substring match), or null (first tab). E.g., tab=0, tab="github.com", or tab=null.'