# Describe: be understood: The Book

> Writing facts, offers and terms so a machine reads them as a person would, and why accuracy is the new brand safety.

Source: https://agentrelations.org/learn/book/describe

Part II: The six domainsChapter summary

A person reading a web page infers a great deal. They know that “from $49” is a starting price, that a photograph of a ramp means step-free access and that the opening hours in the footer apply to the shop and not the warehouse. An agent may infer some of this, slowly and expensively, and get it wrong some of the time. Describe is the craft of removing the guesswork.

The tools are not new. Structured data in the schema.org vocabulary, embedded as JSON-LD, has labeled organizations, products, events and offers for over a decade. Feeds publish catalogs and availability. Newer conventions such as llms.txt offer agents a short guide to a site. What is new is the stakes: an agent repeats what it reads, at scale, to people deciding where to spend money.

What a person reads

“Fresh seafood by the water. Open evenings except Mondays, from five. Book ahead at weekends. Our entrance has a ramp.”

What an agent reads

```
{
"@type": "Restaurant",
"name": "Harbor Kitchen",
"openingHours": "Tu-Su 17:00-23:00",
"acceptsReservations": true,
"servesCuisine": "Seafood",
"amenityFeature": "Step-free access"
}
```

**Figure 5.** The same fact, twice. A person reads the sentence; an agent reads the labeled version without guessing.

Good description has three properties. It is complete: the facts an agent needs to choose are present, including price, availability, terms, location and who the offer is for. It is consistent: the structured data says what the page says, and both agree with the listings elsewhere. It is honest: no inflated claims, because an agent will compare them with reviews and with competitors, and its principal will remember the gap.

The chapter ends with a test any reader can run: ask several assistants about your organization and write down every wrong fact. Each one has a source, and each source can be fixed.

## Read the whole chapter

This is a summary. The full chapter is in the book, which is coming soon. One email when it is published.

Email

Email me when the book is published. Nothing else; ask us to remove you at any time.
