[Google Pixel 7] simplepinoi177:
So, while similar to Samsung SoC and, as I understand it, has some capabilities and features that are shared, there are still many things Samsung is able to do that are not available to Pixels nor can the same utilities be used -- for instance, and most imperatively, ODIN.

While Pixel devices do have an EDL mode, unlike Xiaomi or OnePlus devices, when a Pixel device enters EDL mode, it can pretty much be considered a hard-brick because, unlike Xiaomi and OnePlus devices, there are no consumer-end tools to use & work with and recover Pixels in EDL mode. It seems to be a state only certified techs can use, and even if they can & do have the tools, it usually just ends up replacing the system board anyways with no data recovery avenue offered or given. I've never owned any other devices other than Motorola, Samsung, and Google, but I've heard that other OEMs have it where you can flash a rescue image (partition or firmware), even on a locked bootloader -- and many users from those branded devices that come to Pixels have that complaint on that particular shortcoming. I do wish we had the option as well.

With all that being said, getting your Pixel in such a state (EDL mode) is rare and very peculiar -- those who have reported the issue on an unlocked bootloader is usually user-error, whereas on a locked bootloader it's few and far between and usually is taken care of by Google (warranty, but if not, usually can be negotiated because it was caused by them [in either the hardware to blame or the software update that was pushed that caused it]). Most of the time -- and since I've been active on the Pixel forums since the Pixel 2, I'm talking about well over 90% of the time -- the Pixels only go as far as soft-bricking where it's normally recoverable. After coming from old Motorola's (think original Motorola Droids [1,3,4]) and Samsungs, when I first found that Pixels can go into Bootloader/Fastboot Mode, and flash firmware & OTA images without wiping /internal_sd or /sdcard data -- even so far as flashing particular partitions if need be -- switch slots or other things you can with fastboot commands, I was impressed & shocked & a bit relieved as there were multitudes of ways to recover the device! Honestly, usually a good ol' flashing the Full Firmware image resolves most issues; and it's a very easy process with only a few steps -- most of which is worked & figured out when one unlocks the bootloader anyways. That's why, since the Pixel 2, I've progressed with each Pixel to unlock the bootloader and feeling reassured that I can recover & save/fix my device in most cases.

So, with all that stated and being said in background, to answer directly...

Other than adb & fastboot, no, not "tools" in that sense.

No, unfortunately it cannot "share the same utilities" that "with Samsungs". And, as previously explained, not "tools" per-se.

Honestly, IMHO I feel it really is the most customizable phone (even among other Android phones) and does have huge & active communities (I've been a part of multiple as I've mentioned since the Pixel 2 XL) -- a big part of the reason being that it's one of the most vanilla AOSP Android experiences and easiest to root without too much hassle. Therefore developing custom aspects (ROMs, kernels, themes, etc.) is appealing to developers I imagine.

Some caveats -- gotta make sure that it's a non-carrier variant for the "easiest to root without too much hassle" trait to apply as it's impossible for Verizon variants (and I believe most of the Verizon MVNO's as well) and much more conditions and hoops with AT&T and T-Mobile variants; because unlocking the bootloader supposedly "compromises the security & integrity of the device", you can run into a lot of issues with certain services and apps -> if you're familiar with rooting than you most likely are already aware, but if not; certain Google services like Google Wallet and tap-to-pay, Google Messages RCS is taking a hit right now, Microsoft Teams & InTune, banking apps, Uber Driver app, McDonald's app, some games. There are myriad of ways of hiding unlocked bootloader & root (most notoriously Play Integrity Fix, Shamiko, and Magisk DenyList or MagiskHide), but many companies (Google at the head) seem to be cracking down and making it difficult (See Play Integrity Fix thread).

In the end, there's always the bad with the good to consider.

Hopefully my WOT post helps even though I have to apologize for it being a WOT. Those that are familiar with me know I can get carried away.

But I'm always happy to be helpful....