react-query: Is invalidating query for CUD operations that makes it refetch entities a good tradeoff?

For eg- Lets say I’m using React Query to handle CRUD operations for a to-do list.
After each Create, Update, or Delete mutation, I typically invalidate the GET query so that it triggers a re-fetch of the updated data. This adds an extra API call to GET the latest data, which I wouldn’t need to do if I weren’t using React Query. Before react-query, I was just doing the POST/PATCH and if that returned successful, then I just showed user the updated changes without having to refetch it.

I'm aware that I can probably chose NOT to invalidate queries and not make the extra GET call but I am curious if people see that as a small enough tradeoff (since its quick for the basic cases) in most cases of not having to do all that work?

Note: Asking since I noticed code where people just invalidate their query onSuccess event of the CUD operations. I wonder if that's accepted as a good tradeoff because the extra API call is neglible in most cases?