I think this is exactly where @erlend_sh, @Pad_Pors, and I are coming from. For someone who is familiar with the topic, or frequents the forums often, tags are largely irrelevant/fluff for them. Here are some similar examples (to #pr-welcome) that we use at Stonehearth and could do for some description text.
confirmed_by_users tag added One or more forum members have replied in the thread with the same bug, and has been confirmed to not be an isolated incident.
acknowledged_by_devs tag added : title goes here The bug has been acknowledged by Radiant, and they have added it to the running list of issues to resolve.
resolved tag added The bug has been resolved and the build with the fix has been released.
not_a_bug tag added The reported issue was deemed to not be a bug, but perhaps a misunderstood, intended experience.
not_reproducible tag added The reported issue may be a bug, but the developers were not able to recreate the issue in their testing, and thus cannot fix the error.
no_longer_applicable tag added The reported issue may have been a bug, but the feature and/or code reported is no longer in use, and thus the bug report is no longer applicable.
duplicate tag added The reported issue is the same as a previously reported bug, and the topics have been merged.
That quote is copied directly from our About this category topic, as we needed to explain what the tags are. Giving users the ability to see the description on the tab list, or more ideally, via mouseover, would help decrease how much explaining we have to do for new users.
One or more forum members have replied in the thread with the same bug, and has been confirmed to not be an isolated incident.