I check the discussions, too. There are times where the forecasters have a feeling something is going to happen but they just don’t have enough hard data to justify putting it into the TAF.
Consider a dispatcher working 40 or 50 flights a shift (less than 10 minutes to plan a flight when ya consider eating, peeing, and pooping). They don't have time to read comments on a forecast, just scan the TAF and go. If there is the possibility of MVFR then the tempo would at least flag it for anyone planning a flight.
Of course that's the nature of a forecast, uncertainty. It's always entertaining when the MBA types want to complain about a forecast and don't understand the true risk and costs involved. I was once told in a rather exasperated tone that the estimated return to service for an aircraft on maintenance had to be accurate. Hey, I was just passing along the estimated return to service time that the maintenance controller gave me. The moral of the story is that people don't understand/accept the nature of a forecast (an estimate) and refuse to deal with the uncertainty. Typically, because they can't handle that uncertainty they vent on whoever is available. In other words, the complaint is frequently a response because the complainant doesn't understand the nature of the system and/or can't deal with uncertainty. Should we track forecast failures and try to improve? certainly. I think many businesses overlook that opportunity.
