Agents need contracts, not pages
An agent works best when a tool returns a stable, bounded response instead of handing back a page that must be interpreted from scratch.
Clear input schemas and predictable output records make orchestration easier to test and safer to automate.
Keep provenance close to the record
Source context, timestamps, and explicit missing values help an agent reason about freshness and uncertainty without inventing details that were never observed.
