1 piece
For most model-backed features the output side dominates the cost, because output tokens are priced at a multiple of input tokens and because caching makes repeated input cheaper still. Teams optimise input context anyway, since that is the part they can see and control. Output length is also what drives latency, and the two compound through retries. The fix is to constrain the shape of the answer and to measure cost per completed operation rather than per call.