There is a subtle distinction here that must be made explicit. We must consider two flavors of security definitions:
"Security with Abort": A corrupt party is allowed to see their output, and then decide whether to allow the honest party to receive their output. (I'm describing what happens in the ideal world -- the protocol is secure if every attack against the protocol could have the same effect as some attack in the ideal world.)
An ideal functionality for "coin-tossing-with-abort" does the following:
- toss a fair coin $c \gets \{0,1\}$;
- give $c$ to the adversary;
- wait for a bit $d$ ($d$ = "deliver") from the adversary
- if $d=0$, then give output $\bot$ to the honest parties; otherwise if $d=1$ then give output $c$ to the honest parties.
"Guaranteed Output": A corrupt party cannot prevent an honest party from receiving an output.
An ideal functionality for "coin-tossing-with-guaranteed-output" does the following:
- toss a fair coin $c \gets \{0,1\}$;
- give $c$ to all parties;
The protocol you described doesn't say what should happen if a corrupt Alice fails to open her commitment to Bob's satisfaction. If we tell Bob to abort in that case, we do indeed get a protocol that achieves security with abort. So in that sense, your intuition is correct.
But no matter what you add the protocol, it will not achieve security with guaranteed output.
This is the issue that is discussed in the paper that you mentioned.
For the sake of your question, we define a "naïve" protocol as one with bias 1/2 -- i.e., an adversary can always force a certain outcome with certainty.
You described a protocol in your question and ask whether it is naïve according to this definition.
However, your protocol is underspecified --- it does not describe what an honest Bob should do if Alice's fails (or chooses not) to open her commitment.
So it's not possible to answer whether this protocol is naïve according to this definition.
On page 3 of that paper, they consider the protocol you described, but with the following condition added: "If Alice aborts or does not open the commitment correctly, then Bob should sample his own random bit and use that bit as his output."
They show how the resulting protocol has bias 1/4 and also state that 1/4 is the best attack bias for this resulting protocol.
So the resulting protocol is not naïve according to our definition.