What’s toxic about it? Tickets have a business need. They may have notes on implementation but if they aren’t serving a business need why do they exist?

IMO business needs shouldn't be a ticket - have some refinement first then explain clearly what do you want me to do.

IDK why it's hard for me to explain my sentiment, but I've worked in corp environments with large teams of averages using JIRA vs small teams of smart remote people. In the later my tickets were almost always very clear resulting in 1 or 2 short and tactical meetings per week. In corp environment I have 10 meetings per week spanning hours. The productivity is easily 10x worse.

Exactly. If you are capable enough to file useful tickets you are capable enough to read the code, run it locally, test out changes, tweak copy, etc.

You are wasting money paying people to write tickets and not read code.

I think you have a very narrow view of software development practices. In most companies I've worked at, most tickets are created by the QA team, few of whom have ever seen the source code and there's no reason why they'd ever need to.

They raise a ticket about the problem they encounter, and then other people triage it and try to find a way to reliably repro the issue, and then it gets passed to the development team when there's something actionable.

I've worked in various companies as a developer and my worst experiences were where access to code is restricted, but BA's create these esoteric tickets with about 3 words in description...

I'm happy for them to raise tickets within their realm (and by the way lets not conflate support tickets vs actual work items), but please have some manager sift them thru into something meaningful.