In this analysis
An unchanged token rate can coexist with a changed task bill when reasoning and tool work increase.
Diligence became an explicit cost variable
The July 21, 2026 Flash-family announcement preceded Gemini 3.7 Flash on August 13. The September 2 Gemini 3.8 launch explicitly connected harder work with potentially greater token use. That makes diligence a resource variable rather than a free adjective. Extra investigation can improve an answer, but its usefulness must be judged against the requirement it resolves. An unchanged unit rate does not imply an unchanged bill when the quantity and structure of work change.
Additional steps need an explanation
An illustrative agent investigates a configuration regression. A second source reveals that the apparent fix would break another supported case, so the agent revises its plan. The extra step has a clear relationship to acceptance. Repeatedly rereading the same unchanged log without reducing uncertainty has a weaker claim to value. These behaviors may both increase tokens, but they should not be evaluated identically. The task record should preserve what new information or validation each meaningful step contributed, rather than label all added work either waste or improvement.
Nominal generation speed is not task duration
A model can generate at a similar pace while spending longer planning or making more tool calls. External tool latency and review can also affect the total. A comparison of response throughput alone therefore cannot describe the time to a supported result. This is a general accounting consequence, not a local timing claim. A useful evaluation separates model work, external waiting and validation so that an observed change in total duration can be explained instead of assigned indiscriminately to the new model.
An illustrative investigation trace
A practical fixture provides a regression with a misleading first explanation and a discoverable compatibility condition. Retain the evidence path, proposed fix, validation and usage observations. Compare candidates on whether they resolve the condition while preserving the required behavior. A short but incomplete run remains distinguishable from a longer supported one. No token saving or superiority is asserted here. The fixture tests whether added diligence changes the quality of accepted work, not whether the agent can produce a more elaborate story about its investigation.
Efficiency remains a workload relationship
The September release invites a more precise question than whether a new Flash is simply cheap or expensive. Which tasks benefit enough from additional work to justify it, and where is a lighter route adequate? That question requires actual acceptance evidence. The retrospective lesson is to keep rates, work quantity and task outcome separate until comparison. More tokens can reflect useful discovery, unproductive repetition or changed scope. Only an explanation connected to the task can tell those mechanisms apart and support an appropriate deployment choice.