When a Super Agent loads a List using load_assets, the list description is not included in the returned data. This means any content stored in the list description (pinned @mentions, links to related tasks, contextual notes) is invisible to agents.

Use case: I use the list description to @mention the linked client task for each project list. This is how I connect a project to its CRM record. My Super Agent needs to read this to know which client a project belongs to, but currently has to fall back to fragile name-matching because it simply can't see the description.

Impact: List descriptions are a natural place to store metadata about what a list represents. Without agent access to them, any workflow that relies on list-level context requires workarounds (redundant relationships, strict naming conventions, etc.).

Requested behaviour: Include the list description field (with any @mentions/links resolved) in the load_assets response when loading a List.