I think you are being a bit harsh (no pun intended)...
It is actually very descriptive, the problem is that it's describing what it is and not what it does.
This is quite likely not the case here, but I was in a position once to be working for a really dodgy company without a signed formal contract in place (I know, not ideal, but didn't really had lots of choices) and all variables created were inside arrays. I had an array of int, unsigned int, float, char, etc...
This was all in C, so I had actual description for each bit in a separate file as a bunch of #define instructions.
At the end of the project, I spent a bit of time replacing all of these #defines by the corresponding number and handed them those files as source code. Fully functioning, some comments (not even close to what I consider standard), no compilation warnings, etc...
Obviously, well before they even looked at the code the payment bounced because they didn't make profit off of the project (which I can understand considering how clueless they were on how markets work)... a couple of months later I get a call from the guy saying the code was unreadable and I needed to fix it or give him the real source code. I just pointed to the missing payment and the fact that if it was indeed a loss for the company they wouldn't be using the code either way and he should test things before making claims that it isn't the real code as it is indeed the correct software.
I'm pretty sure he just got another out of Uni guy to basically re-write the whole thing instead of paying (what I now realise) was peanuts.
Not saying that is the case here... but sometimes it's a way to get your money.