Conciseness

The body is mostly efficient and framework-specific with no padding of concepts Claude already knows, but the keysToFetch array (repeated "as CNKeyDescriptor" casts) appears in nearly every code block, and the Common Mistakes section re-examples patterns already demonstrated in the main sections (authorization check, mutableCopy, minimal key fetching). This fits the 'mostly efficient but could be tightened' anchor; it is not 4 because the duplication is more than minor, and not 2 because nothing is generic filler.

Actionability

Every section provides complete, executable Swift (fetch by name/identifier/enumeration, create/update/delete via CNSaveRequest, a full UIViewControllerRepresentable picker wrapper, filter predicates, change observation) covering the common cases. This matches the fully-executable, copy-paste-ready anchor.

Workflow Clarity

The destructive/batch operations have explicit validation: 'execute(_:) returning without throwing is the save success checkpoint', an error-recovery loop (surface the error, correct the known cause, refetch before a corrected retry, never blindly repeat a destructive request), serialized saves, plus a review checklist. The destructive-operation cap at 3 does not apply because feedback loops are present, and the setup-to-observation sequence is clearly ordered via the contents list. This matches the explicit-validation-with-checklists anchor.

Progressive Disclosure

The single bundle reference (references/contacts-patterns.md) exists, is one level deep, and is well signaled twice — inline ('Load Extended Contacts Patterns for multi-select, vCard, and optimized-search workflows') and in the References section — with contents that match the body's advertisement. Advanced workflows are appropriately split out of a navigable, TOC-organized core, matching the clear-overview anchor rather than the minor-gaps anchor at 4.

Specificity

"Read, create, update, and pick contacts using the Contacts and ContactsUI frameworks" names multiple specific concrete actions (the full CRUD surface plus picking) and the exact frameworks involved, matching the comprehensive-coverage anchor. There is no meaningful capability gap that would drop it to 4.

Completeness

The description explicitly answers both questions: what it does ("Read, create, update, and pick contacts using the Contacts and ContactsUI frameworks") and when to use it ("Use when fetching contact data, saving new contacts, wrapping CNContactPickerViewController in SwiftUI, handling contact permissions..."). This mirrors the 5 anchor's structure with concrete trigger phrases; 4 would require the when-clause to be less explicit, which it is not.

Trigger Term Quality

"fetching contact data", "saving new contacts", "handling contact permissions", and "wrapping CNContactPickerViewController in SwiftUI" are phrases users would naturally say, giving good keyword coverage. It falls short of the 5 anchor because common synonyms like "address book" or "contacts list" are absent.

Distinctiveness Conflict Risk

The description is anchored to the distinct Contacts/ContactsUI APIs (CNContactStore, CNContactPickerViewController) with clear niche triggers, so it is unlikely to fire for unrelated skills. It matches the clear-niche anchor rather than the minor-overlap anchor at 4.