repo-map provides 8 well-named, read-only tools with clear verb-noun naming (index, outline, where_is, grep_code, get_symbol, who_references, what_it_uses, refresh). All tools have descriptions (avg ~120 chars, within 10-1024 range). Input schemas are present with typed parameters and descriptions. However, output schemas are NOT documented, the code shows tools return results but no schema definitions are visible in the source. Error handling exists (TargetError class) but lacks recovery guidance. Parameter descriptions are adequate but could be more prescriptive about formats and constraints. No tool annotations (readOnlyHint, etc.) despite all being read-only operations.

• Document output schemas for all 8 tools. Example: outline() returns {file: string, definitions: [{name: string, kind: string, line_start: int, line_end: int}]}. Include in docstrings or via JSON Schema.
• Add readOnlyHint: true to all tool definitions (via FastMCP annotations or schema metadata) to signal these are safe, non-destructive operations.
• Enhance error messages with recovery guidance. Replace 'la cible courante n'existe plus' with 'Target directory no longer exists. Call index(path) with a valid directory, or pass repo=<path> to this call.'
• Add format constraints to parameter descriptions. E.g., 'path: Absolute or relative path to an existing directory' and 'pattern: Valid regex pattern (e.g., r"def \w+")' to guide LLM input.
• Document result limits and pagination. E.g., 'grep_code returns up to 50 matches; use offset/limit parameters to paginate' (if supported) or 'Results capped at 50 to prevent context overflow.'