Conciseness

The CLI instructions themselves are lean and command-driven, but the body carries several padded or dead sections: the leftover "I don't have enough information about Apex 27 to provide a description" paragraph, a "No description" placeholder appearing in all 20 rows of the Popular actions table, and a bare noun-list "Apex 27 Overview". This matches anchor 3 (mostly efficient but includes unnecessary content that could be tightened); it is not 2 because the padding is filler rather than extensive over-explanation of concepts Claude already knows.

Actionability

Commands are concrete and mostly copy-paste ready: "npm install -g @membranehq/cli@latest", "membrane connection ensure \"https://apex27.co.uk\" --json", "membrane action run <actionId> --connectionId=CONNECTION_ID --input '{\"key\": \"value\"}' --json", plus a full proxy flag table. This matches anchor 4; it is not 5 because of minor gaps such as "membrane login --tenant --clientName=<agentType>" showing --tenant with no value, and not 3 because the guidance is genuinely executable rather than pseudocode or high-level hints.

Workflow Clarity

The install → login → connect → poll → search → run sequence is clearly laid out with real validation and feedback loops: poll with --wait until state leaves BUILDING, act on clientAction for CLIENT_ACTION_REQUIRED, re-poll until READY, and check error on CONFIGURATION_ERROR/SETUP_FAILED. This matches anchor 4; it is not 5 because "If the returned connection has state: READY, skip to Step 2" references a Step 2 that is never defined in the document, and not 3 because explicit validation checkpoints for the fragile connection step are present.

Progressive Disclosure

The file has logical section headers but is a ~180-line monolith with no bundle files; the 20-row action catalog (all "No description") and the incoherent Apex 27 Overview belong in a separate curated reference, matching anchor 3 (some structure but content that should be separate is inline). It is not 4 because the document is well past trivial size and mixes catalog filler inline, and not 2 because sections are clearly headed and navigable.

Specificity

"Manage Organizations, Pipelines, Users, Goals, Filters" enumerates several object types but uses a single generic verb ("Manage") rather than distinct concrete actions, matching anchor 3. It is not 4 because anchor 4 requires several specific actions with concrete verbs (e.g. "extracts text, fills forms"), and not 2 because it goes beyond merely naming the domain.

Completeness

Both parts are explicit: what = "Manage Organizations, Pipelines, Users, Goals, Filters" and when = "Use when the user wants to interact with Apex 27 data", matching anchor 4. It is not 5 because the 'when' clause is generic and lacks concrete trigger phrases, and not 3 because 'when' is explicitly stated rather than merely implied.

Trigger Term Quality

The only natural keyword is the product name itself ("Apex 27", "Apex 27 data"), with no synonyms or domain nouns users would naturally say (contacts, listings, leads, tenancies, CRM), matching anchor 3. It is not 4 because keyword coverage beyond the product name is absent, and not 2 because "Apex 27" is a far more specific trigger than generic language like "works with files".

Distinctiveness Conflict Risk

"Apex 27" names a distinct niche product, so overlap risk is low, matching anchor 4. It is not 5 because triggering rests solely on the product name with no concrete trigger phrases, and "Apex" alone risks collision with Salesforce Apex; not 3 because the description is anchored to a specific product rather than a broad category.