Overview:
All 107 events in the ACS Instances Amplitude project (418843) have empty description fields. This makes it difficult for analysts and new team members to understand what each event tracks without reading code or asking engineers.

Why it matters:

• Analysts must guess event meanings or ask engineers
• No way to distinguish active vs deprecated events in Amplitude UI
• Significant onboarding friction for anyone using analytics data

Implementation Details:
Add descriptions to events via Amplitude Data Governance UI. Descriptions should include:

• What triggers the event
• Where in the UI it's triggered
• What properties are attached
• Why it matters for analysis

Acceptance Criteria:

• [ ] All ~50 unique UI events have descriptions added
• [ ] Descriptions follow consistent format (what, where, why, properties)
• [ ] Skip [Segment] duplicate events (those should be archived separately per ROX-32749)

Example description format:
> Fired when a user requests to defer a CVE (temporarily suppress it from reports). Triggered from the Workload CVEs table when clicking "Request deferral". Properties: cve_id, severity, deferral_duration, scope.

Related Tickets:

• ROX-32641 - Amplitude audit that identified this gap
• ROX-32749 - Duplicate Segment events cleanup