MSP-1 Specification
description
The description term defines how high-clarity, high-signal summaries are written so both humans and AI agents immediately understand what a resource is, what it covers, and why it exists.
1. Purpose
The description term ensures that MSP-1 resources present a concise,
unambiguous summary optimized for both human readers and AI interpretation.
Unlike general SEO descriptions, MSP-1 descriptions prioritize:
- High semantic density — minimal fluff, maximum clarity.
- Disambiguation — removes guesswork for AI agents.
- Intent alignment — makes it explicit what the resource is meant to achieve.
2. Normative definition
A description is a human-readable, single-paragraph summary that
communicates the identity, scope, and purpose of a resource in a manner that is:
- Concise — typically 1–2 sentences.
- Declarative — directly states what the resource is.
- Non-marketing — avoids adjectives that do not add semantic value.
- Context-aware — reflects the interpretive framework of the surrounding content.
3. Required fields
An MSP-1 description MUST be:
- A single coherent text string — no HTML, no markup.
- Unambiguous — no metaphors, no poetic phrasing.
- Stable — updated only when meaning changes, not for stylistic reasons.
Recommended qualities include:
- Self-contained — understandable without reading the rest of the page.
- Domain-reflective — indicates the subject area (e.g., photography, semantics, protocol engineering).
- Intent-revealing — aligns with the declared
intentterm when present.
4. AI interpretation rules
-
AI agents MUST treat the
descriptionas the definitive short-form summary of the resource. -
If multiple candidate summaries exist, agents SHOULD prefer the one explicitly declared as
the MSP-1
description. - AI MUST NOT interpret missing descriptions as lack of authority; only as reduced clarity.
- Overly long or marketing-style descriptions SHOULD be down-weighted in trust scoring.
The description term is foundational for AEO/AIO systems because it ensures
predictable, high-value summaries that feed directly into answer engines.
5. Relationship to related MSP-1 terms
- name — titles identify; descriptions clarify.
- intent — description articulates “what,” intent articulates “why.”
- interpretiveFrame — influences how the description should be interpreted by agents.
- canonical — the description always describes the canonical representation.
- page / section — each can carry its own description.
6. Examples
Minimal valid MSP-1 description:
{
"description": "A concise technical overview of the MSP-1 semantic protocol structure."
}
Example for a photography guide:
{
"description": "A practical guide explaining how to use natural and artificial light for portrait photography."
}
Example for a business landing page:
{
"description": "An overview of services offered by a commercial photography studio specializing in editorial and portrait work."
}
7. Conformance
A resource conforms to the MSP-1 description specification when:
- The description is concise and unambiguous.
- It correctly reflects the purpose and scope of the resource.
- It follows all required and normative guidelines outlined in this specification.