Speaking as an employer and hiring manager (e.g. not an HR person...), I find tool listings incredibly helpful -- a person's choice of tools, or lack thereof, tells me something about the person. That something is typically positive, but it can be negative as well. For example, if a candidate says they're "a HTML/CSS rockstar ninja" and lists their favorite editor as FrontPage, I'm going to question that. But usually I use the information as an entry point into the conversation.
For example, regardless of experience level, when I interview candidates I always ask a question about IDEs. What that question is will depend on what they do or do not list, of course, but if someone says they use Eclipse, I'm going to ask them how. What plugins? Have you written any plugins of your own? What feature do you like best/dislike, and what functionality can you not live without, and why? Things like that. I like to hear people talk about their relationship with their IDEs (good or bad), because I learn a lot about their processes and workflows.
And for more mundane reasons, it's nice to know if a person will "fit" with the rest of the team's choice of IDE, because it makes pair programming easier, and general discussions about development practices have the same foundation. That's not at all a requirement, but it's a good piece of intel.