Planning poker, story points, etc. are not an intrinsic part of agile (or even Scrum, from what I understand). Honestly, I'd not use them at all because they're not worth the time investment.
"Agile as a whole" does not require planning poker, or story points, or burndown charts, or Fibonacci estimates, or Kanban boards, or any of that. Neither does Scrum. Google "Agile Manifesto" and "2020 Scrum Guide."
If it isn't in the 4 values and 12 principles, it's not required in Agile. If it isn't in the guide, it isn't required in Scrum.
> I'm not totally sold on the whole points poker process though, but that could be a criticism of agile as a whole.
My understanding of agile is give your developers the tools they want, the information they want, and the ability and incentive to communicate widely, quickly, and frequently however they want, and get out of the way. You have to devolve responsibility and accountability for meeting business goals down to the team level though, and that team has to act as one.
None of that has anything to do with "points poker process", or any process. Obviously everyone has a process, even solo developers working on their own hobby, but that process is "what works best".
I'm not totally sold on the whole points poker process though, but that could be a criticism of agile as a whole.