I'd like to suggest a documentation improvement for the Assets endpoint reference.
The search query parameter on GET /brandfolders/{brandfolder_id}/assets is currently documented generically, with no indication of what can actually go inside it. The fact that you can filter by custom fields (custom_fields.{key}:"value"), tags, sections, and combine them with boolean operators is only documented in the Recipes / Searching guides.
From a developer perspective, the Assets endpoint is the natural entry point when you're trying to fetch or filter assets - not the Recipes section. As it stands, a developer reading the Assets reference has no way of knowing these capabilities exist without stumbling onto the guide separately.
I'm not suggesting you duplicate the full search syntax on every endpoint that supports search. But it would significantly improve discoverability if the search parameter description on /assets surfaced - at minimum - that it accepts field-qualified queries, with one or two concrete examples (e.g. custom_fields.Channel:"E-Mail") and a link to the full syntax guide.
