Three tools with Korean descriptions and partial schema coverage. save and undo have input schemas (Zod-defined with optional params and descriptions), but descriptions are in Korean and lack English clarity for international LLM use. status has no input parameters. All three tools lack documented output schemas. Error handling is present (hardStopBlocked, isGitRepo checks) but recovery guidance is minimal. Tool naming is verb-based (save, undo, status) but descriptions do not clearly state when to use each tool or what they return. No parameter constraints (enums, ranges) beyond optional flags. Composition is reasonable (three distinct concerns), but output structure is not documented for LLM planning.

• Translate all tool and parameter descriptions to English. Korean descriptions block international LLM adoption and violate pattern:tool-description baseline (100% of A+ tools have English descriptions).
• Document output schemas for each tool. E.g., save returns {preview: string, executed: boolean, commit_hash?: string, push_status?: string}. This enables LLM planning and chaining.
• Expand tool descriptions to 80-150 chars. Include WHAT (commits changes), WHEN (before pushing code), and CONSEQUENCE (irreversible unless undo called). Current descriptions assume LLM knows git semantics.
• Add error classification to hardStopBlocked and isGitRepo responses. Return {error: 'hard_stop_active', action: 'ask_user_to_resume', reason: '...'} instead of plain text. Enables agent recovery logic.
• For save/undo, document the confirm:true opt-in pattern in tool description, not just parameter description. LLMs need to see the safety gate upfront: 'Destructive operation, requires explicit confirm:true parameter.'