Should prototypes have the actual descriptions and help text?

I'm prototyping a couple of fairly complex web screens. Each field in these screens has its own label, description, and a question mark (?) icon next to it —The question mark icon displays additional information and examples when clicked.

I'm trying to decide whether the description and the help text in the prototype should be the actual content I mean to have in the end result —as opposed to just some lorem ipsum.

On the upside, it would make the prototype a one-stop shop for the developer. But on the downside, it feels an awful lot like hardcoding. In SW development you always decouple the UI from the text using i18n files of some sort. Should the same apply to UX design?