Operating steps
- Detect repeated fields, descriptions, enum values, and examples.
- Mark fields needed for initial routing versus fields needed at call time.
- Generate a slim schema manifest and a full on-demand manifest.
- Verify sample tool calls still satisfy required input contracts.
Common risks
- Removing required-field explanations can increase tool-call retries.
- Nested objects need examples somewhere, even when not eagerly loaded.
- Client compatibility should be checked before changing schema delivery.