This MCP server has fundamental definition quality issues. All three tools (list, read, write) have minimal descriptions (under 20 characters baseline threshold) and lack proper input parameter documentation. Tool descriptions are trivial ('List directory contents on remote server', 'Read file contents from remote server', 'Write file contents to remote server') and do not meet the 10-1024 character guidance for LLM-optimized descriptions. Parameter schemas are present but lack descriptions, the 'path' parameter appears to have a description in the schema, but parameter descriptions are sparse and generic. The 'write' tool is particularly concerning as it handles state modification (WRITE risk) but lacks any mention of confirmation, dry-run, or error recovery guidance. No tool declares permissions (read:filesystem, write:filesystem), no tools provide pagination or limiting, and error handling is not visible in the tool definitions themselves. Tool naming is acceptable (verb_noun style: 'list', 'read', 'write'), but the composition lacks sophistication, no idempotency guarantees stated, no output schema documentation visible in definitions, and no guidance on what happens on retry.

• Expand each tool description to 100-200 characters. Include: WHAT it does, WHEN to call it, WHAT it returns, and any state-changing side effects. Example: 'list: Returns directory contents (names, sizes, types) from a remote path. Use before read/write to discover available files. Fails if path is not a directory or lacks read permission. Safely retryable.'
• Add detailed parameter descriptions. For 'path': 'Absolute or relative path on remote server (max 4096 chars, forward slashes, no null bytes). Tilde expansion not supported. Path must be accessible by the SSH user.'
• For 'write', add a description: 'File content to write (max 10MB text/binary). Overwrites existing file atomically. On failure (disk full, permission denied), the file is not modified. Safely retryable with same content.'
• Document output schemas for each tool. Specify: list returns {files: [{name, size, type, mtime}]}, read returns {path, content, encoding}, write returns {path, bytes_written, mtime}.
• Add permission/scope declarations to all tools. Example: list requires 'read:filesystem', write requires 'write:filesystem'.
• Add error handling guidance. For example, in the write tool description: 'On permission denied, suggests checking SSH user's file permissions. On disk full, suggests freeing space before retry.'
• For 'path' parameters, define constraints: 'Must be a valid absolute path (starting with /) or relative to SSH user's home. Max 4096 characters. Must not contain null bytes or control characters.'