Since the name of the application is a description about what it does (hence the app really doesn't have a proper name), then it should be translatable.

This is not a dillemma.

Your very simple application can have a proper name (e.g. "Catorize"), but since what it does can be described in one short sentence, it's more informative and prominent to display that as the name ("Puts menu icons into proper categories"), making it more discoverable for end-users, and we don't care about brand recognition. We sometimes don't have much of a UI (or any UI for that matter) that users can identify with, so even more so (Catorize or my package).

Your single-purpose application or an application the purpose of which can be described in two, three words ("gPodder Podcast Client") can have a proper name, but the name is still descriptive, which is good. The description should still be translatable ("Klient podcastów gPodder").

Then there's the third category of apps, which don't have focus on a specific purpose, they're like a Swiss army knife (e.g. "Tweakr"), or the mechanics of which cannot be easily described (some games), so you can get away with having just the proper name in the name field, but you still need the description in the description field and I can almost guarantee that even the basic functionality description provided by the application will not fit there, so the end-users will have to be adventerous to take a look at your work (that obviously doesn't truly affect e.g. games).