Fleet's MCP server has critical definition gaps. All 4 tools have schemas with proper JSON structure and type declarations, but descriptions are minimal (10-20 chars) and lack actionable context. Tool names are verb-based (read_file, list_directory, grep, echo) but descriptions are in Korean and extremely terse, providing no guidance on WHEN to use each tool or what downstream operations expect. Parameters lack descriptions entirely in most cases (e.g., 'path' in read_file has a description, but 'pattern' in grep lacks context on regex syntax). No output schemas are documented. Error handling is absent, no guidance on recovery, retryability, or what to do when a file is not found. The echo tool appears to be test-only and should not be exposed in production.

• Translate all descriptions to English and expand to 50-150 characters. Example: 'read_file' → 'Read a text file from the workspace. Returns file contents as a string. Use this to inspect source code, configs, or documentation. Path is relative to workspace root.'
• Document output schemas for all tools. E.g., list_directory should return {items: [{name: string, type: 'file'|'directory', size?: number}], total: number}. grep should return {matches: [{file: string, lineNumber: number, content: string}], totalMatches: number}.
• Add parameter descriptions for all inputs. E.g., grep.pattern: 'JavaScript regular expression (case-sensitive). Enclose in / / for flags, e.g. /pattern/gi for global+case-insensitive.' list_directory.path: 'Directory path relative to workspace root. Omit or pass empty string to list workspace root.'
• Add error handling guidance. E.g., read_file: 'Returns error if file not found, is binary, or path escapes workspace. Try list_directory() first to verify the path exists.' grep: 'Returns empty matches if pattern has no results. Invalid regex returns error with syntax hint.'
• Remove echo tool from production. If needed for testing, gate it behind a feature flag or separate test-only MCP server.