I agree that this is a good design philosophy. But I also think that the problem of "the user not reading the app description" (as described by the parent) is

I agree that this is a good design philosophy. But I also think that the problem of "the user not reading the app description" (as described by the parent) is a separate issue. For example, I found that there were several problems to be solved that were all related to the same domain. Apps existed that do a decent job of solving problem X. So I wrote an app to solve problem Y. I have received numerous 1-star reviews because the user is disappointed that my app does not solve Problem X. In my case, I am pretty confident that I clearly described the problem solved by my app. I even explicitly say that it is not meant to solve problem X. I have also received many positive reviews from users looking for an app that solves Problem Y. So in my case, I don't think it was a problem with understanding the user.