My main rule is: Never write a class that you can't use again.
I've other rules too, such as "padding is top, margin is bottom".
CSS must be modular, not exception-based.
To visualize it, http://hicksdesign.co.uk/boxmodel/ is probably the most oft-cited example - certainly the one I find most helpful.
more info: http://reference.sitepoint.com/css/collapsingmargins
This is not true of padding (unless you count a bug in IE8 where percentage-based padding-bottom collapses on the margin-bottom)
In that case, use margin.
When you have complex pages, with several nesting levels, this can save much, much time.
Now you've got comments saying in correct things, and you risk all sorts of confusion.
The same rule applies to commenting methods in code really, you don't comment what the code does exactly - just what the intention of the code is.