What this means in practice
This context helps it form a query against the actual schema instead of guessing field names.
You can ask about the data without pasting the schema into every prompt.
Practical guidance
Before answering, the agent receives a summary of the available schema: collection names and counts for NoSQL, and table names and columns for SQL. This gives it concrete field names to work with, reducing the chance that it invents a column or collection based on an ambiguous request. It also means you do not have to paste the same schema into every prompt.
You still get better results when you describe the question you want answered and clarify unfamiliar business terms. Schema visibility tells the agent what structures exist; it does not tell it what every field means or which records matter to your decision. If a query produces an unexpected result, check whether the requested concept maps to the right table, collection, or column. Clear domain context complements the structural information supplied automatically.