Three tools with basic verb-noun naming (read_file, list_directory, search_content) and short descriptions (10-60 chars). All have input schemas with type and description fields. However, descriptions are minimal and lack context on when/why to use each tool. No output schemas documented. No error handling guidance. Parameter descriptions are terse. Tools are read-only and safe, but lack the depth expected for production use.

• Expand tool descriptions to 100-200 chars. Example: 'read_file: Read the full contents of a file. Use this to inspect source code, config files, or documentation. Returns raw text; for binary files, returns an error. Max file size: 10MB.'
• Document output schemas explicitly. E.g., 'Returns: string (file contents)' for read_file; 'Returns: list[str] (one entry per line, format: "path:lineno: line_content")' for search_content.
• Add error classification and recovery hints. E.g., 'If path is outside BASE_DIR, try a relative path from the project root. If file not found, use list_directory to explore available files.'
• Add constraints to 'path' parameter: 'Relative path from project root (max 255 chars, no absolute paths, no ../ traversal). Examples: "src/main.py", "docs/README.md".'
• Add limit and offset parameters to search_content to enable pagination. Document default limit (e.g., 100 results) and max limit (e.g., 1000).