Conditions decide which work items a rule touches once the trigger fires. Here the condition is a JQL query evaluated against the one work item that fired the event. If the item matches, the actions run; if not, the rule records nothing and moves on.
Write the narrowest condition that still covers the request. A routing rule without a project clause can reach every project the actor can see. A rule that assigns high-priority work without checking assignee IS EMPTY will overwrite an owner someone chose on purpose. Remember that assignee != milo silently skips unassigned work, exactly as it does in search, so say IS EMPTY when blanks matter.
Test a condition the way you test a search: think of the record that should not match and make sure it does not. The checker here replays your rule against many invented work items, so any condition that selects the same work passes, however you order the clauses.
Write the narrowest condition that still covers the request.