Which is ridiculous, because Hamcrest has very good descriptions for its matchers that can even be queried for their description without running the matcher. The matchers in this library only describe themselvees on failure.
The real issue here is that the abilities created here are primitive compared to the wide variety of powerful Matchers available in Hamcrest.
I am not even saying that you have to eliminate what is here, just allow Hamcrest matchers to be used as well. Although with Kotlin extension functions, ti is probably trivial to add it myself.