Some of the advanced query parameters in API calls such as $search and $count require setting a ConsistencyLevel request header. This is unintuitive to developers working with MS GRAPH API , arguably it isn't what request headers were designed for.
It's very unusual to enable query options using headers. The problem is amplified by a poor documentation that fails to mention the header in many places.
The header is required to opt in for eventual consistency. This is just one way to achieve that.
Without knowing the nature of your backend architecture, it doesn't seem like a huge challenge to detect advanced query parameters in the URL, without requiring a header.
From a user perspective is feels like an overengineering. As user I want simplicity and clear documentation, which is not the case here and it made me spend a lot of time to figure this out.