Looking at the tag you assigned to the question, I would point out that this is actually not boolean logic, but three-valued logic. Implementations of such models must necessarily make arbitrary choices regarding their constructs, and in the case of OData, it seems that "something that isn't false must be true".
I suppose this is in part because more people would be confused otherwise, and in part because most other implementations work that way too.
As far as I know, there is no shortcut for your use-case (you must check both conditions explicitly).