Earlier quoted context omitted.
Sometimes one just needs a direct answer to a question. In fact, it’s a common anti-pattern of effective communication, to think that “more detail ( all the detail ) is always better.” Sometimes we just need an answer to the question, and will ask follow-ups as needed. I find a correlation actually where people who struggle to give clear answers/explanations, struggle in their own decision-making. They get ensnarled…
All the examples you've given are of team members struggling in a wider ecosystem. Yes, you can stamp your foot and hold them to their responsibilities on a single task. But you might deliver more value if you listened to the things holding them back, because there will always be future tasks.
But some people struggle to collect their thoughts clearly, and struggle to articulate simple answers to even the simplest of questions. I have seen this, and seen how detrimental it is to their effectiveness as engineers and teammates. My approach is to actively coach people on my team that I see with poor communication.
And it's a valuable skill that I'm advocating. When an engineer is invited to a VP presentation, and the VP asks "Has this feature launched?", you better believe they don't want a 3-minute ramble of the challenges they faced, or what they'd do differently, or whatever. They want to know: "Has. This. Feature. Shipped?"