Elliott exposes 12 tools with minimal quality standards. All tools have basic descriptions (10-50 chars), but lack critical structure: NO input schemas are visible in the source code, only parameter names and types are listed informally. Parameters lack descriptions entirely. Output schemas are undocumented. Tool names are generic (e.g., 'files', 'terminal', 'ssh') without action verbs. Critically, 7 of 12 tools accept credentials (passwords, tokens, API keys) as parameters, a severe security violation. Error handling is absent. This server would fail code review by any production standard.

• Define formal JSON Schema for every tool's input parameters. Include type, description, enum constraints, min/max bounds, and regex patterns. Example: {"type": "object", "properties": {"root": {"type": "string", "description": "Absolute path to root directory (must exist)", "minLength": 1}}, "required": ["root"]}
• Move all credentials (passwords, tokens, API keys, private keys) out of tool parameters. Inject them server-side via environment variables or a vault service. Update tool parameters to accept only non-sensitive config (baseUrl, hostname, account ID). Document the required env vars in a README.
• Rename all tools to start with action verbs: 'files' → 'read_file' + 'write_file', 'terminal' → 'execute_command', 'ssh' → 'execute_remote_command', 'smtp' → 'send_email', 'pihole' → 'query_pihole_dns', 'traefik' → 'configure_traefik_route', 'vault' → 'read_vault_secret', 'cloudflared' → 'provision_cloudflare_tunnel'.
• Add 50-150 character descriptions to every parameter. Example: 'root: Absolute filesystem path where file operations are sandboxed. Must be an existing directory with read/write permissions.' Avoid generic names like 'config' or 'data', be specific about what the parameter controls.
• Document output schemas for every tool. Specify return type (object, array, string), field names, types, and which fields are required for chaining to other tools. Example: 'Returns {"success": boolean, "file_path": string, "size_bytes": number, "created_at": string (ISO 8601)}'. Include pagination (limit, offset, total_count) for list tools.