While that might seem useful at first glance (and it’s indeed puzzling why there’s no parity between iOS and macOS versions at that point – there shouldn’t be technical hurdles to it), it would go against the nature of an HTML document’s description if saved as a bookmark.
A bookmark is just a reference to something else. That something else can change (and many websites do change). The description of a website, ie the corresponding meta element, can also change.
What you (seem to) want is a snapshot, at least of the description. In that case, saving the HTML document as such (formatted note) might be a better approach. That gives you a snapshot – the document on the server may well change in the future, with its description.
The only (in my opinion) sensible alternative to that would be to have DT load the relevant HTML documents regularly and possibly update their descriptions in its index. Which might put a considerable performance burden on it.
I do save web articles as pdf or SingleFile html. But my scenario here is to store the link to a site (like GitHub repos, home page of a software, or a custom wiki). In this case, it does not make sense to store the page content because it always changes, but I do need a way to search the bookmark among like 1000+ other github repos. And the title alone may not be enough.
Anyway, the idea of @meowky should do the trick: use a smart rule that copies the description to the comment field without overwriting that. You could run that on clipping, on sync or on demand.
That is correct and also what Criss mentioned: “In case of bookmarks the information is actually grabbed live from the currently previewed web page but it’s not stored/indexed information.”
