I disagree with the answers by @LarrySnyder610 and @Michael Feldmeier.
Operations Research and optimization are about what's best (under uncertainty), or at least better. Let people answer with their opinion of what's best and why. Make the thread Community Wiki if necessary, so as to keep the Stack Exchange powers that be happy (enough).
Sometimes (in real life work) I like to mention options which are bad, and explain why, because the bad options might otherwise be pursued. Should I just list a bunch of options, including ones I know are bad, and not say anything about that? Or are pros/cons o.k. as long as you don't say what's best? - I think that would be silly
Unlike the actuary profession, Operations Research is not cut and dried, and does not have a formal body of rigid rules for everything. Discretion is allowed and encouraged - that is part of what attracted me to the field, and away from consideration of being an actuary.
In my experience on related Stack Exchange sites, such as Cross Validated/ and Math Overflow, Community Wiki posts with answers about software and other tools and resources addressing particular needs, and with these answers containing people's opinions and rationale, are some of the most useful threads . Unfortunately (in my opinion), there are almost always a couple of law and order types arguing about those threads.
In summary, let people state their opinions and rationale. Make the thread Community Wiki if necessary.