It does not give descriptions or representations, given congressional districts. It requires a completely disjoint input: postal districts. So unless you recommend a counterpart district-to-ZIP lookup tool, I can't see how it's useful for a description of districts because you still need to know which ZIP codes are within it to do so. Strange that the webapp doesn't use permalinks, or allow unique identifiers of districts as a search variable, no? This makes it largely unuseful for this contextual district-to-(neighborhood-level)map/description requirement.

> As to your weak attempt to make this about class, I'll point out West Virginia's congressional district Google Maps overlay

Well, it was more of a statement about using anecdotal examples which are not representative of congressional office websites. (It could be a statement about class, but this was not my point.) It's obvious the offices are doing these maps themselves because there exists no viable alternative, and it still appears uncommon for the offices to do so. While my remarks may be inflammatory, it is nonetheless evident that your suggestion to direct the users to congressional office websites (or dozens of unaffiliated and state and local websites), as well as a ZIP-to-district tool, would be ineffective in this context.