I think the big (only?) advantage that GraphQL has in this case is you get "API documentation" out of the box as a frontend developer. The tradeoff is that I n

I think the big (only?) advantage that GraphQL has in this case is you get "API documentation" out of the box as a frontend developer. The tradeoff is that I need to use GraphiQL or similar tooling to leverage this auto-complete, type-safe magic and that using curl becomes more painful. I'm curious: Suppose you converted your REST endpoints into GraphQL endpoints in the simplest way possible by changing the query-params to root GraphQL nodes. So there's no "graph" really. Just lots of top level nodes. This reduces the API docs overhead and nothing else. Would you switch? Is your existing tooling to extract API docs already good enough that this isn't a problem?