From our accessibility consultant we've received the feedback, that role=tooltip should only be used on static tooltip content.
If the content has actionable items, it should be using a different role, to expose the interactivity clearly.

WCAG 2.1 is not explicitly outspoken about it, but this discussion provides a clearer feedback on why it's not a good idea to have interactive elements or even ”complex structured content, as it's read out 'in a oner' by AT”.

Update 2019-05-29

Changed from “Evaluate” to “Remove” due to the findings in resources above.

We should remove role=tooltip. In current state the previews are not properly exposed to screen readers anyways, as there's no machine-readable clear connection between the calling link and the preview, see T220777.