Your token bill gets uncomfortable, and the qualification agent is still reading featureId . Somewhere, a hexadecimal identifier has acquired a consulting budget.

Lab note 004: we wanted to know which fields a lead qualification prompt actually needs when the listing schema exposes 24 fields.

The catch comes early: inspecting a schema can justify a smaller context contract. It can't establish a token-savings percentage or an improvement in scoring accuracy. Those need measurements on your records and your qualification task.

What does the scorer need to decide?

Suppose you're building a queue of coffee shops in Austin for email outreach. The agent needs to assess category fit, apparent location, public reputation, and whether there's evidence of an email contact.

It doesn't need to decide which database identifier looks most official.

Our bet is a projection containing title , categoryName , address , totalScore , reviewsCount , and emailsMxValid .…