add chained expectation descriptions to the default descriptions of custom matchers with fluent interfaces

this fixes #532
Yes that makes sense, especially since the decision to include the chained clauses can be done when description is invoked.