Something to keep in mind about all this (and something that my wife reminds me of when I get annoyed trying to write product descriptions) is that the description and the product are separate. In that, if I struggle to write a description that is attractive to everyone, it doesn't necessarily mean that the unattracted ones won't like the product. And some that are attracted to the description will dislike the product.

This is just part of the difficulty of marketing; you can't please everyone. You have to figure out what problems the bulk of your possible user market are trying to solve that your app solves, and present that plainly and concisely. Flowery language tends to obfuscate; just plain simple "If you have problems XYZ, this will solve those", then link to greater detail about how each of X, Y, and Z, are solved.

It's hard to do this because we are so used to seeing mid level manager bullshit PR speak on every product page we look at; it seems like a requirement. I've had very refreshing experiences with product descriptions written by a technical writer who just did not give a fuck. Just wrote it up like he was sending an email about a bug report, published it, and it was fantastic.