I personally hate having to use so many tags, but until Nuget.org start supporting newlines, it's hard to put the required keywords into the description, and unless the right keywords are present, users can't find the package.
I love NuGet, but searching for packages right now is nearly impossible unless you know the exact name.
I opted for the approach of using Tags and leaving the description readable, but I'll be thinning those tags out as soon as NuGet supports Markdown or HTML.
All of the tags listed are relevant to the package. If there are some you don't think are relevant, let me know, and I'll explain. Some may be too generic or too specific, perhaps, but they're all relevant to features of the package series.
I went through each tag and made sure each one was needed to support searching on a known search query - the only tag I should probably remove is 'redirect', as I don't remember why that was in there. Perhaps it was part of the CloudFront redirect feature...
I'm all for hiding all but the first 10-20 tags, but we need a better way to make packages searchable.