I agree with almost everything except point 1. A Minimum Viable Product is exactly that-- the smallest possible product that will be viable in the marketplace. Some startups and developers may take this thinking overboard and put products on the market that are so stripped down as to not be viable, but I think that the concept of a true MVP sums up the entire purpose and challenge of Product Management.

A true MVP must strike the balance between feature bloat and watered down junk, driven by a vision of what users need as opposed to what they think they need. Such vision requires a lot of insight and a lot of courage. Imagine being the PM that decided the iPhone was ready to ship without support for copy and paste. Is copy and paste an important feature for a mobile phone? Obviously. Was it necessary for the product to be viable in the marketplace? Clearly, it wasn't, and that is why determining a feature set for and MVP is such a challenge.