Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% across six parameters, so the description carries the burden and largely drops it. It hints at the codigo and texto parameters via 'um código ou termo', but says nothing about tabela being mandatory alongside codigo, the mutual exclusion of codigo and texto, the limite default of 20, include_expired, or the date parameter's role.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.