No matter how you spin it TDD is busy work for programmers. If its your only documentation then fine. Otherwise you have to write twice as much code for something that will be deprecated in a year.
It can be considered busy work, but if it’s busy work that finds bugs and makes the debugging process easier, then it’s a win in my book. I’d rather write tests than debug
In your book because you have organised your entire workflow around it.