Maybe I was a bit too harsh on your request, and for that I apologise. The main reason I thought you wanted us to write a full specification was because you had a full template written up, and to be frank it wouldn't be the first time someone posted their work on a public forum and subliminally asked someone to do it for them,.
All things you'd expect a front-end person to do, although unless you've got a lot of work to do this may be a bit limited. I've known entry-level designers come in, design a site and code it ready for back-end development within the space of two days.
This is why I'm always inclined towards hiring a designer rather than a developer, one that can create the design itself in Photoshop and then code it.
I would probably change this to show that the developer would follow a company-set quality standard, because at the end of the day whoever you hire will be doing important work for the company and their manager needs to have some form of input on the work.
I'm always a bit iffy when it comes to asking for n years experience. I would probably change this to say that previous development experience, with a portfolio of work for clients or for themselves is essential. It's important to stress that the developers skills will be judged on the quality of their portfolio, so that great designers with little experience aren't discouraged.
If I were you I'd scrap the jargon and simply say that you require someone to write semantic, standards-compliant front-end code and someone proficient in user-interface design using graphics tools like Photoshop. Leave the interviewee to tell you what they think standards-compliance is and you'll have a better idea of whether you'd want that person working with you.
The last thing you need is some bozo to read your job description, pick up enough to get through the interview and drag your business down.
I'd probably include some stuff on source control (something everyone should have).
Honestly, how much information do you believe you'll get from the answers to these questions? If someone doesn't follow any blogs or resources does that make them a poor developer? Do you really care where they see themselves in ten years?
If I were you I'd keep it short and sweet by just having a general conversation about the work they've done. If they've used a lot of jQuery press them on that. If they've been between jobs for a while ask them if they've read up on much web stuff since they last worked, etc. You'll learn a lot more by going through the candidates previous experience and picking holes in it.
Absolutely not. If anything, I'd expect them to be designing the websites themselves, and be open to the idea of learning source control for their projects.