Private trackers that use this often fill in a three letter code specific for their tracker. Users that upload torrents can add it themselves (using dottorrent-gui for example) or the tracker will add it and the uploader needs to download the torrent with added tag from the tracker to start the seeding. Often people use different a locations for uploads than the default download location. So they will have to move files or edit download location and do a force recheck. If it would be implemented in the normal torrent creation process it would be much easier especially for novice users.
If if was not clear this is done to be able to cross-seed the same content between different private trackers. If no difference is made between the torrents the tracker addresses of the 2nd torrent will be added to the first and the seeders of both trackers will be mixed by the client.
Basically, the purpose of it is to differentiate exactly same torrents on different trackers so peers from a different tracker can't come on another tracker ("peer-leak").
For me, adding these lines worked for creating a torrent or reading a torrent, I don't know if there's anything missing.
coverage: 98.353% (+0.02%) from 98.329% when pulling dcd55521e3b3a3fa398f8a337207e97243a988da on kickturn:master into 9079c1ddd436af5b969685e5a4cfda02a2ee8d0c on idlesign:master.
This issue from qbittorrent explains it well
Basically, the purpose of it is to differentiate exactly same torrents on different trackers so peers from a different tracker can't come on another tracker ("peer-leak").
For me, adding these lines worked for creating a torrent or reading a torrent, I don't know if there's anything missing.