I completely second you Sanjay. But the core question is who write it. As per my understanding customer write it. The same team write the defiant ion of done after having discussion with customer. But I read the opposite some where,

For the user story, the acceptance criteria are the PO’s vision and therefore are the PO’s responsibility. The acceptance criteria forms the user story's technical requirements and describe the expected functionality. They are the “what” of the user story. The Product Owners owns the Product Backlog and stories inside it.

PO can take help in writing user stories as individual & interaction support in maximum contribution from all the team members. But the final call is taken by the PO. So who writes it? - for the answer the PO is the answer, however, we cannot ignore the collaboration.