Writing the LLM Description
Describe the job, not the file.
Every resource has an LLM Description. The hint under the box says what it is for: this is what the AI reads to decide when to include this resource in deals, content, and communications.
It is worth taking literally. When SI is deciding what to attach to an email, it is not looking at your image. It is reading your description of it. A resource with no description is a resource SI has almost no reason to pick.
Steps
Say what it shows or says
One clause is enough. "A one-page comparison of our three service tiers with prices."
Say when to use it
This is the part people skip, and the part that does the work. "Use when someone asks what the difference between the plans is, or when they have gone quiet after a quote."
Say when not to use it
Constraints are read as constraints. "Do not send to existing customers — the pricing shown is for new business only."
Mention who it suits, if it matters
If the resource is pitched at a particular kind of reader, say so in the description as well as setting the audience scope. The scope controls eligibility; the description shapes judgement.
Result
A described resource gets chosen at the right moment and left alone at the wrong one. An undescribed one tends to sit unused — or turn up somewhere it does not belong, because nothing told the AI otherwise.
Info: Nobody outside your team reads this field. It never appears in an email, on a deal page or on your website. Write it as a note to a new colleague who is about to answer your inbox for you.
A description worth having
- Says what the resource contains
- Says the situation that calls for it
- Says who it is not for, if that is a real risk
- Avoids repeating the title back
- Reads as an instruction, not a caption
