The everyday problem
A collection of clean examples can hide the behavior that matters most in daily work. Missing documents, contradictory fields, and unusual responses may determine whether a workflow is usable. An evaluation that excludes these cases tests a narrower problem than the team will eventually operate.
A practical approach
Create categories for routine, incomplete, conflicting, and unsupported inputs. Define the expected response for each category, including when the system should stop. Review errors by category so that a strong average does not obscure a failure in a critical exception path.
Try this with your team
Add one deliberately incomplete fictional example to your test set. Specify the clarification or escalation you expect before running the test.