Preserving Order in Tool Definitions: JSON vs JSONB Solutions

Hi, I'm encountering an issue with tool definitions. In my tool, some parameter keys are dependent on others, as referenced in their descriptions—so the order of keys is important. However, Phoenix stores tool definitions in a JSONB column, which automatically reorders the keys (typically by key length), and this is causing the tool to malfunction. Is there a way to preserve the key order or work around this issue? Also, would it be possible to use a JSON column instead of JSONB to maintain the original key order?