As Darrell said, you should exclude the Forms user account to prevent it from triggering on the other conditions. Also, if you only want the Create rule to trigger based on the Forms process, you can do the opposite and only allow it to run if the user equals your Forms user.

Another option instead of the Move condition would be to set the workflow as a Business Process, which would give users the ability to add a button they can use to force the workflow to run. You can set conditions on those as well that only allow certain users/groups to run the process and require certain metadata fields/templates.

Another tip on Workflow starting rules is to always include the "Repository Name equals" condition. If you ever end up with multiple repositories, which is quite common, the extra condition (at the very beginning) will help Workflow identify which rules apply to which repository to prevent unexpected triggering.

I already applied the Business Process addition on the next version of this project.  It to me seems to work the best as well.  But even so I wanted to investigate this as it doesn't seem like normal behavior.

If Forms does create then change the document after to add metadata, it would in fact kick off the process twice.  If that is what is happening here.