No, not authoritative.
It disables "strict search hash checking". This is most commonly used to workaround issues resulting from some query parameters being changed in-flight during multi-page ldap queries.
Here is an example:
"Could not connect to a directory server" error message when you click the “last page” button in the search results in Exchange Server 2007 OWA
Note that there is a dsHeuristics attribute in Active Directory, and that is very well documented in the Active Directory Technical Specification.
More information from here:
"When the original request is executed, the system builds a string, called a “search argument signature”, and hashes it. The resultant hash is then stored with the restart argument. When the second page is retrieved, the restart argument is queried and the “search argument signature” is recomputed and hashed. If the new hash does not match the stored hash, the system fails the request."