LGTM, one minor remark only.

Looks good to me.

Here's hoping the needed changes are soon made and committed to Master, I see it potentially going quite a ways in reducing the need of trying to look up information in the docs. or on Blenderartists (as long as one tries to keep tooltips inside of 2 lines, or 3 lines for complex operators). I know that tooltips are not intended to be documentation, but as of now you even have to look up information for some of the small stuff.

This would also go hand in hand in creating tooltips for operators that don't have them as of now due to how they would become easier to write. I know I've looked at tools where I wished it had a better tooltip (or actually had a tip).

Talked on IRC and this should really be handled in BLF, using some API calls,
eg:

• BLF_draw_wrap(..., width),
• BLF_boundbox_wrap(..., width, &nlines);

Then any part of blender can request some wrapped width to draw into and BLF can do the rest.

Edit, BLF_boundbox could be used in this case, so words just wrap at the bounds.

Some suggestions for API...

• BLF_draw_lines (like BLF_draw but supports \n)
• BLF_draw_wrap (like BLF_draw, but split at word white-space word boundaries), using the boundbox.
• we would want a function to return the number of lines too (I think BLF_width_and_height_multiline(..., &nlines))

having _multiline suffix all over isnt ideal,

Uploaded a new diff which implements word-wrapping in BLF. D1493