It would be nice to have more detailed instructions in the Evergreen CLI download page for first-time users who haven't already done these steps before and/or are not familiar with how to actually get the binary to run the first time on MacOS.
1. When the Evergreen CLI gets downloaded, it might not have executable permissions and new people might not know to do chmod +x on it.
2. Since we don't sign our binaries, the first time someone downloads the Evergreen CLI, MacOS will complain that it's an unsigned binary and won't let you run it until you change the security permissions (System Preferences -> Security & Privacy -> General -> "Allow anyway").