One very strong consideration is this.
How is your PC connected to the internet? That is a factor in being able to connect back to it from a remote location. If it is, as the majority are, on a home style network using a private IP address range such as 192.168.0.0/24 then it is difficult to connect directly to that machine from the internet.
If instead you are connected directly to the internet and have a public IP address that is easily accessed from the internet it becomes easier to connect, but much higher risk from attackers.
There are ways to work around both styles of connection, but it does require that the user be aware of the issues and be able to properly manage the connections – securely. That is even before you would need to become concerned with the remote desktop experience (which will never be the same quality as when directly at the console).
Your laptop probably has a better direct desktop experience than would be possible with remote access to the PC. This is the nature of access across a network where you have no control of the hardware or software or connection speeds or other users hogging the bandwidth.
There are multiple client apps supporting RDP including GNOME Connections and Remmina.
The latter also allows tunneling RDP and VNC over SSH, although setting up a VPN is preferable.
Hey, it’s been a while since I looked into this topic but thank you for your answer I didn’t know that were clients supporting RDP on Linux. Ultimately, I decided to use tailscale to establish my connections. Now I have another problem, when I connect to my PC using gnome connections i get blank screen that turns glitchy after a while. I just wonder what could go wrong. The only thing I did is uncommenting Xorg section in /etc/xrdp/xrdp.ini and commenting Xvnc section.