Mixed-quality server with 22 tools spanning tetris game logic (12 tools) and filesystem access (10 tools). Tetris tools have Japanese descriptions (non-English, limiting LLM utility) and minimal parameter documentation. Filesystem tools are better-structured with English descriptions and proper schemas, but many lack depth. Average description length ~120 chars (below 194-char baseline). Parameter descriptions often missing or trivial. No output schemas documented. Error handling absent. Naming is generally verb-first but lacks clarity on tool relationships.

• Translate all tetris tool descriptions to English and expand to 50-150 characters, explaining WHAT the tool does, WHEN to use it, and any side effects. E.g., 'clearCurrentBoard' → 'Clear all pieces from the current tetris board. Resets the board state without affecting page history.'
• Document output schemas for all 22 tools. Specify field names, types, and what data each field contains. E.g., getCurrentBoard should document that it returns a 2D array of strings where '_' = empty, 'X' = obstacle, 'I'/'O'/'L'/'Z'/'T'/'J'/'S' = tetromino remnants.
• Add parameter descriptions to tetris tools. E.g., setColor: 'Color number (1-8) mapping to tetromino types: 1=I(cyan), 2=O(yellow), 3=L(orange), 4=Z(red), 5=T(purple), 6=J(blue), 7=S(green), 8=X(gray)'. drawPixel: 'X coordinate (0-indexed, 0 to board width-1)' and 'Y coordinate (0-indexed, 0 to board height-1)'.
• Implement dry-run or confirmation patterns for destructive operations (reset, removeAllNextPage, write_file, edit_file, move_file). E.g., add a 'dryRun' boolean parameter (already present in edit_file) to all write operations, returning a preview of changes before committing.
• Add actionable error messages with recovery hints. E.g., 'Invalid page number 99: board has only 5 pages. Use getPageCount() to check available pages.' or 'Pixel coordinates (50, 30) out of bounds: board is 10x20. Use valid coordinates 0-9 for X, 0-19 for Y.'