You aren't going to teach them a new language because you don't want to learn theirs.
I think it's really important that the designers at least understand the points that are controlled in CSS. You don't have to annotate in valid CSS but the terms you use need to be clearly related for the UI developers. Why invent a new vocabulary?
Here's an example of how I would communicate a button style.
Menu button normal state
- background color (for no-gradient fall back): #ccc
- background gradient: light (top) #eee / dark (bottom) #999
- border color Top/Btm/Lft #999 / Right #eee
- font: Verdana, 11px, 1.2em line height, normal weight, #333
- type shadow: no blur, #eee, offset 1px up
- padding (all sides): 12px
- corner radius (all corners): 4px
That would be in a doc followed by a graphic example of the item in question. Depending on the team, I use Evernote or a Google doc on Drive to share it.
I always aim to provide the development team with a clear set of reference materials.
- Static mocks with no overlaying info.
- The same with very basic notes overlaid as necessary.
- Isolated mock-ups for features that involve interaction, like the example above.
It's a short list if the project is straightforward. For big projects, I might provide them with multiple pages of running CSS instructions and dozens of graphic snippets in addition to the main static comps and any production assets required.