Added value: +false

Previous value: -"Your own scratch space on this asset — prompt, model, seed, source job id, anything you need to recognise it in a later session. Playbook never interprets it. Max 4096 BYTES of serialised JSON; anything larger is REJECTED, never truncated. A write REPLACES the whole object, so read the asset first if you mean to keep existing keys. You can read it back per asset (get_asset, or list/search with get_ai_payload=true) but you CANNOT search or filter on it — do not try to find assets by payload contents."New value: +"Free-form JSON metadata stored with the asset — for example generation settings such as model and seed, or a source job id. Playbook never interprets it. Max 4096 BYTES of serialised JSON; anything larger is REJECTED, never truncated. A write REPLACES the whole object, so read the asset first if you mean to keep existing keys. You can read it back per asset (get_asset, or list/search with get_ai_payload=true) but you CANNOT search or filter on it — do not try to find assets by payload contents."

Removed value: -{
-  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
-  "type": "string"
-}

Previous value: -"Custom field values, keyed by field name: { \"Priority\": \"High\" }. For an option field, both the field name and the value must match an existing field and one of its options EXACTLY (see list_custom_fields) — the API skips anything it cannot match and still reports success, so verify the returned `fields` map. Typed fields take a plain string instead: a date field an ISO date (YYYY-MM-DD), a person field a member token (from list_members), a url field an http(s) URL; \"\" clears a typed field, and an unparseable value fails the whole update. list_custom_fields gives each field's `field_type` and exact name. Each supplied value REPLACES the asset's previous value for that field; custom fields omitted from the map remain unchanged. A value written on a group also applies to its members."New value: +"Custom field values, keyed by field name: { \"Priority\": \"High\" }. For an option field, both the field name and the value must match an existing field and one of its options EXACTLY (see list_custom_fields) — one that does not exist comes back as an error naming the valid fields or options, while the rest of the update is still saved. The built-in Status field is set with `status`, not here. Typed fields take a plain string instead: a date field an ISO date (YYYY-MM-DD), a person field a member token (from list_members), a url field an http(s) URL; \"\" clears a typed field, and an unparseable value fails the whole update. list_custom_fields gives each field's `field_type` and exact name. Each supplied value REPLACES the asset's previous value for that field; custom fields omitted from the map remain unchanged. A value written on a group also applies to its members."

Previous value: -[
-  "token",
-  "context"
-]New value: +[
+  "token"
+]