no - i think you missed my point. i definitely did not intend for this to be an additional user-specified custom field - i agree that there would be no value in that.
rather, what i had in mind was that pushover notifications behave more like the other built-in notifications such that instead of every pushover having exactly identical description with the fixed string "send push notification", that the description be a more descriptive auto-generated description based on the parameters of the pushover action {title (opt), message (can contain variables), sound (opt), priority (opt), device (opt), Link (opt), Link Title (opt)}.
if you check, you can see that nearly all of the built-in actions populate their descriptions based on the settings/parameters. here are some examples of action descriptions:
send email to
duff@alum.mit.edu; subject "fire in the kitchen!"
turn on device "Exhaust Fan"
send push notification
the code snippet i included is from the validateActionConfigUi method, which implies that it has access to all of the user-supplied parameters at the time when the user is done entering them and thus seems like the ideal code point for the description to get set.