In leveraging the DAB Sql MCP server, I have run into various behaviors that I would like the mcp server to provide additional guidance to the consuming client instead of having each consuming client encode the same behavior.

The ask would be to add a Description or Instruction field in the dab-config.json file that the MCP server that could appended to the different tool descriptions. For example, on the read_record tool, you would be able to extend the tool description by adding "If the user does not provide an order by, default to sorting by the column Created descending". This prevents duplication to every entity or Created field in the json file.