Deagle-server exposes 6 tools with basic descriptions and partial schemas. Tool names follow verb_noun convention (search, map, sg, rg), which is good. However, descriptions are minimal (10-50 chars), parameter descriptions are sparse or missing, and output schemas are not documented. The 'map' tool lacks clarity on what 'dir' parameter does when optional. Error handling and recovery guidance are absent. No tool annotations (readOnlyHint/destructiveHint) despite clear risk profiles. Schemas present but incomplete, many parameters lack type info or descriptions. This is typical of early-stage code intelligence tools but falls short of production quality.

• Expand tool descriptions to 50-200 chars. Example: 'search' → 'Search for symbols (functions, structs, classes) by name in the indexed code graph. Returns matching entities with file paths and line numbers. Use fuzzy matching for typo tolerance.'
• Document output schemas for all tools. Example: search returns [{name, kind, file, line, score}]; map returns {indexed_files, indexed_symbols, duration_ms}.
• Add parameter descriptions for 'dir' (default behavior), 'kind' (valid enum values), 'pattern' (syntax examples). Example: 'dir: Directory to search (default: current directory). Relative paths are resolved from the server's working directory.'
• Add tool annotations: readOnlyHint=true for search/stats/sg/rg/health; destructiveHint=true for map (since it modifies the graph database).
• Add error handling: 'If search returns empty, try a shorter query or use sg/rg for pattern/regex search. If map fails, check directory permissions and file encoding (UTF-8 required).'