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

this fixes #532
Yes I was debating whether to set it to nil or false, but setting to nil seemed to show that you can set it back to it's default value.  false may be clearer for this test's purpose, since the test is about setting it to false