Give the Data Business Meaning

The agent doesn’t need a dictionary for every CRM field. It needs the definitions that change a decision. Start with the two values that broke Acme’s answer.

A useful definition changes behavior

renewal_risk_score is not helped by “the renewal risk score.” The agent can infer that from the API name. Give it the scale, thresholds, direction, and update behavior:

field: renewal_risk_score
meaning: Predicted renewal risk from 0 to 100. Higher is worse.
values: 0–39 low, 40–69 medium, 70–100 high
updated: nightly

That entry earns its prompt space because it changes the conclusion. Select the risk-score definition in the lab and rerun the Chapter 1 question.

Field labels are interfaces, not rules

Labels are written for people who already know the business process. “Account health” does not say who maintains it or whether anything still reads it. Add that missing operating fact. The agent can now explain why two fields disagree instead of quietly choosing the friendlier label.

Start from existing help text

Export the descriptions your CRM admins already maintain. Keep the ones that explain the field well. Write new context only for missing definitions, stored-value mappings, stale processes, and other details that alter an answer.

Add at least the risk-score definition in the lab. A complete exercise produces a different conclusion from the same CRM record.

What changed

The CRM data did not change. The model did not change. You supplied one durable business definition, and the agent stopped reading 82 as a positive score. Chapter 3 will add authority and freshness so that conflict resolution becomes explicit.