If the start point is ambiguous, every person on the team invents a different mental model of how the tool runs.
Naming the pitfall early helps you design tests, reviews, and safer boundaries. Connect the idea to a realistic coding decision so recall is easier when solving similar questions.