Wikifier has 18 tools with basic naming and descriptions, but significant gaps in schema completeness and parameter documentation. Most tools accept only 'project_root' (optional string) with minimal constraint info. Descriptions are terse (10-60 chars) and lack actionable context for LLM selection. No output schemas are documented. Error handling and recovery guidance are absent. The server is functional but falls short of production-grade tool design.

• Document output schemas for all 18 tools. E.g., session_bootstrap should return {root: string, health: {status: string, metrics: {...}}, actions: [{id: string, title: string, ...}]}. Use JSON Schema in tool definition.
• Expand tool descriptions to 100 - 200 chars. Include WHEN to call, WHAT it returns, and any prerequisites. E.g., 'check_changes: Scans project for modified files (yellow) and orphaned docs (red). Call after editing to assess impact. Returns status map and file list.'
• Add parameter descriptions with constraints. E.g., 'project_root: Absolute or relative path to project root. If omitted, uses WIKIFIER_PROJECT_ROOT env var or auto-discovers from .wikifier marker. Must be a valid directory.'
• Add tool annotations: mark record_change, mark_green, update_maps with destructiveHint=true. Mark all read-only tools with readOnlyHint=true. Mark idempotent tools (e.g., get_file_wiki) with idempotentHint=true.
• Document error cases and recovery paths. E.g., 'If file_path not found, returns error with suggestion to call list_paths(prefix=...) to discover valid paths.' Use pattern:recovery-guide.