Server has 7 tools with complete schemas and descriptions, but quality varies. File tools (list_files, read_file, overwrite_file, create_file) have proper async implementations and access control, with 50-100 char descriptions. Internet tools (internet_research, get_url) have detailed descriptions and reasonable parameter sets. Simple greet tool lacks depth. Output schemas are implicit (JSON dicts returned) but not formally documented. Error handling is basic, returns status/error dicts but lacks recovery guidance. No tool annotations (readOnlyHint/destructiveHint) despite clear risk distinctions (READ_ONLY vs WRITE). Parameter descriptions are present but some lack constraint details (e.g., safesearch enum not explicit in schema, timelimit format unclear).

• Add tool annotations: mark list_files/read_file/get_url/internet_research with readOnlyHint=true; mark overwrite_file/create_file with destructiveHint=true; mark create_file with idempotentHint=true (checks for existence).
• Document output schemas in JSON Schema format. For list_files, define {status: string, roots?: array, files: array<string>, message?: string}. For read_file, define {status: string, content?: string, message?: string}.
• Enhance error messages with recovery guidance. Instead of 'File not found or access denied', return either 'File not found. Try calling list_files() to find the correct path.' or 'Access denied. Filepath must be within allowed roots: [list].' Categorize errors as retryable vs user-fixable.
• Add enum constraints to internet_research schema: safesearch as enum ['off', 'moderate', 'strict']; timelimit as enum ['d', 'w', 'm', 'y', null] or with regex pattern.
• Implement pagination for list_files: add limit (default 50, max 500) and offset parameters; return {files, total_count, has_more} so agents can request subsequent pages.
• Add file size limits and document them: read_file description should state 'Returns file content up to 10 MB; use max_chars to truncate.' Validate and return helpful error if file exceeds limit.
• Add dry-run support to overwrite_file: new optional parameter 'dry_run' (default false). If true, validate permissions and return {status, changes: {old_length, new_length}} without writing. Update description to note this capability.