What you call "Buzzwords" many would call technical jargon.
Jargon is a shorthand way of communicating quickly with others who understand it.
You see "Buzzwords" in are building every website in AJAX, MVC, REST, and HTML 5, where as I think "I wonder if the MVC is a front end Javascript MVC framework operating against the REST backend, or if the model & controller parts are shared by the REST and AJAX front ends, but have different views?"
I know you meant it as an example, but to me it was a perfectly legitimate description of a development stack.
So starting with "we are an HTML 5 AJAX shop..." I would roll my eyes, where as compared to "Our stack makes heavy use of REST methodologies..." I would mull the description.
I guess its a level of understanding that goes into the use of the terms.
If I were describing a technology stack, it would include the actual development language and further specific, relevant details. That might include the exact example as given, but the example standing on its own still ranks low on the desirability scale.
Also, my description would exclude "building every website in".
At one level, like Google aggregating signals, responding to an abundance of buzz words is one of several ways to classify a given posting as promising or not. A few buzz words could be fine, but a company actually saying they "are building every website in AJAX, MVC, REST, and HTML 5" all in the same sentence is definitely problematic.
Separately, I think there are people who use buzz words to earn points among their non-technical colleagues, which seems to be cultural appropriation from programmers. You can also see this with words that have been redefined in pop culture, like 'hacker'. This naturally breeds resent and wariness of buzz words in general.