When does using GraphQL for internal APIs just make things more complicated for no good reason?

Weve been talking about using GraphQL for some of our new internal services, especially for how our backend services talk to each other. It's nice that GraphQL is flexible and has strong typing. That would really help with APIs that are always changing. But it also feels like it makes things more complicated. You have to deal with schema management and resolvers, and you might run into N+1 problems. Simpler REST or gRPC endpoints might not have those issues, especially if the services are already pretty close or need very specific data. So, how can you tell if GraphQL is just too much for internal APIs? Or is it something we should think about even then?