I see you have little experience with Scrum...

Acceptance criteria is a human-readable text that the person specifying the software has to write to fill-up a field in Scrum tools and not at all guide the work of the developers.

It's usually derived from the description by an algorithm (that the person writing it has to run on their mind), and any deviation from that algorithm should make the person edit the description instead to make the deviation go away.

> Acceptance criteria is a human-readable text that the person specifying the software has to write (...)

You're not familiar with automated testing or BDD, are you?

> (...) to fill-up a field in Scrum tools (..)

It seems you are confusing test management software used to tracks manual tests with actual acceptance tests.

This sort of confusion would be ok 20 years ago, but it has since went the way of the dodo.

As someone quite familiar with human-run project management and Scrum, I believe parent was posting quite facetiously.