The "not an answer" flag states:
This was posted as an answer, but it does not attempt to answer the question.
The Seagate answer started out saying "this did not work for me, but doing something else did". It may not be a great answer, and it could do with some care, but it is attempting to provide a solution. It might be entirely wrong, or odd, but an attempt was made.
The SSH one is again trying to provide more information that may or may not be useful, it looks like it could be edited into the existing answer but it does give information on what the tools asked about in the question can be used for:
Check your keys with ssh-add -l
You can stop the current ssh-agent session with ssh-agent -k
Something to know about ssh-agent and .bashrc is don't load too many keys. The default number of tries for ssh daemon is limited to 6. This can been modified in /etc/ssh/sshd_config with the MaxAuthTries value.
In this case I think it is half adding to the existing answer, and half adding new uses for the tools requested. If anything the question is too vague.
In both cases the flags were rejected because the answers were trying to provide some kind of solution or help.
Moderators are not the arbiters of what is correct, and you should not be using flags to tell us that you think that something is simply incorrect. If it is not even vaguely an answer, as in it is explicitly trying to talk to another user or about another subject entirely, then that is when you should use the "not an answer" flag. If it is trying to help, but ending up as unintelligible gibberish then flag as very low quality.
If, on the other hand, you believe an answer is simply wrong or unhelpful then you should comment and/or downvote it.