I don’t know. From my experience I get pretty good descriptions of PRs if I ask the right questions and provide some context.
That's pretty much what a PR description is.
I guess you could also use all the session rollouts saved to disk that were related to that task, and distill them somehow.
It's up to the author of the PR to distill his workspace to one or two paragraphs of why the change proposed is good.