The problem with leaving little to assumption is that this tends to be verbose and people tend not to like to listen to long speeches and will simply not read long text. So, as everything in engineering, it's a tradeoff.
My spouse gets frustrated with me for being too verbose in my requests, and also frustrated with me for following instructions in "the wrong way" when those requests were under-specified in the first place. Knowing "the right level" to communicate requests can be challenging in any relationship, even one with 20 years of shared experience to fall back on.
I micromanager will work around that by splitting the requirements up in tiny jira tasks that cannot be ignore easily, and then follow up daily on every single task.
This completely kills initiative, tough, and may reduce the value added by each team member by 50% or more.
The only time to use such tactics is with someone who is acting in very bad faith and at risk of being fired. It can be done for a while to establish an example, while rewarding better behavior with more autonomy gradually.
If they still ignore the instructions, then that's proper grounds for firing them (even in Europe), and if they chose to leave because of it, well, that's ok too.
