Three well-defined read-only tools with complete schemas, clear descriptions, and proper parameter typing. All tools follow verb_noun naming (repo_map, search_code, pack_context). Descriptions are substantive (100-180 chars) and explain WHAT, WHEN, and WHY. Input schemas use Zod with type constraints (min/max for integers, string length). However, output schemas are not documented, LLMs cannot predict response structure. Error handling returns generic text without recovery guidance. No tool annotations (readOnlyHint, idempotentHint) despite all being read-only. Parameter descriptions are good but could be more prescriptive about formats and constraints.

• Document output schemas for all three tools. Specify fields, types, and nesting (e.g., repo_map returns {tree: string, entrypoints: string[], fileCount: number}).
• Add tool annotations: set readOnlyHint=true and idempotentHint=true for all three tools to signal safety to LLMs.
• Enhance error messages with recovery guidance. E.g., 'Path not found: /invalid/repo. Verify REPO_CONTEXT_ROOT env var or pass absolute path to root parameter.'
• Add format constraints to parameter descriptions. E.g., 'root: absolute or relative filesystem path; must be a directory. Defaults to REPO_CONTEXT_ROOT env var or cwd.'
• Consider adding cursor-based pagination to search_code for large result sets (e.g., next_cursor field in response, cursor parameter in input).