An open discussion during the specification workshop builds a shared understanding of the domain, but the resulting examples often have a lot more detail than is really needed. Customers often think about the system from the perspective of the user interface so they will offer examples of how something should work done at the level of clicks and filling in fields. Using such verbose descriptions overconstrains the system and already specifies how something should be done, rather than just what is to be done. Surplus details make the examples harder to communicate and understand.
Examples need to be cleaned up and focused in order to work efficiently as specifications. Good examples define what should be done with enough detail to implement and verify it, but without any additional information.