As I understand it, you pass your current span ID to the remote RPC endpoint, it continues adding to it from there, creating their own nested spans etc.
When it gets back to you and all spans are merged, you can see the whole picture, but don't need to provide all the details all the way down.
I still don't get how trances/spans are shared across rpc boundaries but I know that's a thing one can do.