Our design calls for a “Most assets” sort option on the shares list and for showing how many assets each share contains directly in the list view.
The Share schema exposes no count field, and there is no documented include that adds one, so both of these are impossible - not merely inconvenient. Counting per-share by fetching each share’s contents doesn’t scale as a list-view solution.
Requested: asset_count on the Share object (by default or behind an include), plus a matching sort value so it can drive both the display and the ordering.