Token usage is down, but task completion is also down. How would you evaluate the optimization?

Instruction: Explain how you would judge a token reduction that may have gone too far.

Context: Tests how the candidate diagnoses the problem, chooses the safest next step, and reasons through recovery. Explain how you would judge a token reduction that may have gone too far.

Official answer available

Preview the opening of the answer, then unlock the full walkthrough.

I would call it a failed optimization until proven otherwise. Lower token usage is only valuable if the workflow still succeeds at the required quality bar.

Then I would identify what was lost: grounding, completeness, clarification behavior, or robustness on harder requests. Token savings often...

Upgrade to view official answer

Related Questions