When is using a message queue just overthinking things for services to talk to each other?

Hey everyone, I've been thinking about how services talk to each other. We always hear that message queues are super important for keeping services separate, dealing with too much traffic, and making sure things are reliable in big, spread-out systems. And yeah, for really busy, async stuff, they're definitely the way to go. But for smaller, less important chats between microservices, is a message queue always the best option? Sometimes it seems like adding a queue just makes things way more complicated and creates more places for stuff to break. I mean, you have to worry about messages that dont go through, the order of messages, and watching the queue itself. Maybe a simple HTTP call or a basic pub/sub would be enough. What do you all think? Are there specific situations or times when you decide not to use a message queue and go for something easier, even with microservices?