It isn't your job, nor are you obliged in any way to report anything you find.
However, a video recording of an issue is standard in publisher-run support forums, which are often completely separate to the developers themselves (this is also the case in regular software, to greater or lesser extents). I had to record videos of glitches in BL3, back in 2019 - 2020. Games are more complicated than ever, and run on more machines than ever. It's not a given that the support team could reproduce it on whatever hardware they have available to them, and to even gets to the devs, support need to be able to reproduce the behaviour (because they will add additional information that you have no reasonable way of knowing, that'll aid development in repro-ing and fixing the issue in-house).
So sure. You don't have to do anything. But at the same time, your expectation that somebody should be able to repro it from a description alone is flawed. Even if this is the case for simpler issues, or issues that reliably reproduce, the support team will have a standard expectation for supporting materials for any submitted issue. They can't handwave that because it looks straightforward. They have to follow procedure.
If support at my work handed development a ticket with a text-based description and zero supporting evidence, we would close the ticket. Because support haven't followed procedure, and it's a waste of development's time to do support's job (in addition to dev not interfacing directly with customers, which puts up an additional barrier in obtaining said supporting evidence).
Hopefully this insight helps a bit. Again, I completely agree you're under no obligation to do anything. But these procedures, these requests for data, exist for very valid reasons.
And back to lurking I go.