Jeff, I can tell you two things. I love it when local writers review courses because they usually make a complete botch of it and review hole by hole how a pro plays the hole - bearing no relationship to how real golfers do. I've also always followed a rule of writing - never describe a golf hole. Readers who haven't been there won't get it and readers who have been there won't need to revisit. Hack writers also make a serious mistake when they judge a course or a hole on the basis of how well or badly they play it.
It's also good to avoid a whole bagful of cliches: signature design; championship course; signature hole; playable by all classes of players; risk/reward; minimalism, "Open Doctor," "build it and they will come;" a course you could play every day and never get bored; links-style.
Generally, I try to convey how the place looks and makes golfers feel, and sometimes I'll convey a hole in terms of its aesthetics and the sensibility it evokes, as well a sits local cultural flavor. I also try to convey a sense of the developmental journey by which the land was converted from whatever it was to whatever it has become. And I also think it helpful to indicate a few obvious weaknesses, since every course has them.
Comparing to other courses in the architect's repertoire or to other, similarly-styled courses can always help. I think it helpful to remember that most of the readers who rely upon these have not been to the course, are not championship goflers, and are simply trying to decide if it's worthwhile for them to go. The tug has to be emotional and aesthetic, not technical.
Along the way, I also try to be a little didactic, that is to teach readers a little about the nature of design, about criteria of good and bad design, and how to evaluate courses, and how this one I'm reviewing fits into the overall set of standards and critieria.