feat: chatbot prefers structured trip fields over editorial text

docs/chatbot-mcp.md

@@ -44,6 +44,11 @@ that prices and availability are a snapshot (`dataAsOf`) and only the booking pa
 | `search_content` | Questions not about dates or prices | Up to 8 hits with a ~600-character excerpt |
 | `get_document` | The full text of one `search_content` hit, by `url` | Markdown body, truncated at 20 000 characters |
 
+Editorial text (product descriptions, FAQs, pages) is maintained by hand in TYPO3 and can lag behind BusPro, e.g. an
+old price or a changed inclusion. The server instructions and the tool descriptions therefore tell the model that the
+structured trip fields of `search_trips` and `get_trip` override whatever the text says about dates, prices, pickups
+and inclusions.
+
 Every result carries the public `url`. Output is compact JSON with Markdown in the text fields.
 An empty result is `{"results": []}`. Invalid input produces a tool error the model can read.