Server has 7 tools with complete JSON schemas and basic descriptions. However, descriptions are minimal (10-50 chars, well below the 194-char baseline), lack actionable context, and omit critical safety guidance for destructive operations. Parameter descriptions are present but terse. No output schemas documented. Error handling returns generic JSON errors without recovery guidance. Tool naming follows verb_noun convention but lacks clarity on resource types (e.g., 'mega_delete' doesn't distinguish file vs folder). No tool annotations (readOnlyHint, destructiveHint) despite having READ_ONLY, WRITE, and DESTRUCTIVE operations. Missing idempotency guidance for retry-prone operations like upload/download.

• Expand tool descriptions to 100 - 200 chars. For mega_delete: 'Permanently delete a file or folder from Mega.nz. This action is irreversible. Confirm the file name before calling. Returns success or error with reason (e.g., file not found, permission denied).'
• Document output schemas in tool descriptions or as a separate schema field. E.g., mega_list_files returns {items: [{name: string, type: 'file'|'folder', size: number, modified: ISO8601}], total: number}.
• Add tool annotations: readOnlyHint=true for mega_storage_info, mega_list_files, mega_search; destructiveHint=true for mega_delete; idempotentHint=true for mega_upload (if overwrite is idempotent).
• Enhance error responses with recovery hints. E.g., 'Upload failed: quota exceeded (used 950GB/1TB). Call mega_storage_info to check usage, or delete old files with mega_delete to free space.'
• Add parameter constraints to descriptions. E.g., mega_upload: 'local_path must be an absolute file path (e.g., /home/user/file.txt). File must exist and be readable. Max size: 20GB.' mega_search: 'query must be 1 - 255 chars. Wildcards (*) supported.'