Find the Webflow CMS fields that trip up your editors

**Objective:** Audit the field schema of the Webflow CMS collection named `{collection-name}` and report the fields that are likely to cause editor mistakes or broken content.

**Step 1: Resolve the collection**

Call `webflow-get-collection` with `display-name` set to `{collection-name}`. If nothing matches, retry with `display-name.contains` set to `{collection-name}`. If more than one collection matches, list each match (display name, slug, collection-id) and stop. If none match, say so and stop.

**Step 2: Read the fields**

Call `webflow-get-collection-field` with `collection-id` set to the collection-id from Step 1 and `max-records` set to 200.

**Step 3: Assess each field**

* Required fields (required = true) with an empty help-text: editors get no guidance on a field they cannot skip.
* Fields with editable = false: note them so nobody expects to change them through the Designer or CMS.
* Reference and MultiReference fields: these link to other collections and break silently when the target item is removed.
* Image, File and RichText fields that are required: these block item creation from simple imports.
* Display names that are unclear, duplicated, or differ from the slug in a way that will confuse API users.

**Step 4: Report**

Start with one line: the collection's display name, slug and total field count. Then a table with columns Field, Slug, Type, Required, Editable, Issue, covering only fields with an issue, most serious first. End with a short list of recommended changes.

**Rules & Guidelines:**

* This is read-only. Use only `webflow-get-collection` and `webflow-get-collection-field`.
* Do not guess what a field is for when its name and help-text do not say; mark it as unclear instead.

**Validation:**

* If the collection has no fields, report that and stop.
* If no field has an issue, say the schema looks clean and give the field count by type.