No tool descriptions explain error recovery, prerequisites, or when to use each tool vs alternatives. Naming is acceptable (verb_noun pattern) but descriptions are generic. No output schemas documented. Error handling is absent, no guidance on retryability, user-fixable vs fatal errors, or recovery steps.

• Add parameter descriptions to fs_write: 'path' (relative to server root, no ../ traversal), 'contentBase64' (standard RFC 4648 Base64), 'append' (if true, append; if false, overwrite).
• Add parameter descriptions to server_command: 'command' (full command line without leading /, subject to whitelist/blacklist in config.yml; blocked commands return error 'Command not allowed').
• Document output schemas for all three tools. E.g., server_logs returns {lines: string[], totalLines: int, truncated: boolean}; fs_write returns {bytesWritten: int, path: string}; server_command returns {exitCode: int, output: string, error: string}.
• Add error recovery guidance to fs_write and server_command descriptions. E.g., 'If write fails due to permissions, check server directory ownership. If command fails, verify it is in the whitelist via config.yml.'
• Clarify fs_write security: 'Path must be relative to server root and cannot contain .. or absolute paths. Parent directories are created automatically. Returns error if path traversal is detected or disk space is insufficient.'