Ease of use is my top priority - if a tool is hard to learn, it's hard to get adoption across the team. Would you say that's true for your team as well?
I'd pick Community support - a strong community can help with troubleshooting and best practices. What about documentation quality, though? Should it be an option?
I'd pick Community support - often it's the community that helps you troubleshoot and find creative ways to use the tool, even if the official docs are lacking.
I'd pick Community support, because having a strong user base and active developers can make a huge difference in long-term maintainability and troubleshooting.