Codegeist provides 5 file-system tools with complete JSON schemas and clear descriptions. All tools have proper input schemas with typed parameters and descriptions. Naming follows verb_noun convention (codegeist_read, codegeist_edit, codegeist_grep, codegeist_glob, codegeist_list). Descriptions are concise (20-80 chars) and action-oriented. However, descriptions lack context about when to use each tool vs. alternatives, and parameter descriptions are minimal. Error handling and recovery guidance are not visible in the provided code. Output schemas are not documented. The codegeist_edit tool (WRITE risk) lacks confirmation/dry-run pattern for destructive operations.

• Add output schema documentation for each tool. Example for codegeist_read: {type: 'object', properties: {lines: {type: 'array', items: {type: 'object', properties: {lineNumber: {type: 'integer'}, content: {type: 'string'}}}}}}
• Expand tool descriptions to include when to use each tool. Example: 'Use codegeist_grep to search file contents by regex pattern. Use codegeist_glob to find files by name pattern. Use codegeist_list to explore directory structure.'
• Add format constraints to regex/glob parameters. Example: 'Java regular expression (e.g., ^class\s+\w+ for class definitions). Invalid patterns return a syntax error with position.'
• Implement dry-run or confirmation for codegeist_edit. Add optional 'dryRun' boolean parameter that returns the diff without applying changes, or require explicit confirmation before destructive writes.
• Document error cases and recovery paths. Example: 'If pattern syntax is invalid, the tool returns error code INVALID_PATTERN with the position of the error. Retry with a corrected pattern.'