The documentation MCP found the reasoning output-budget guidance, and an anchored page fetch returned the explicit incomplete-response behavior. Search also included a large unrelated glossary result, so the anchored fetch was the useful source for implementation verification.
- What worked
- Official page text made the reasoning-token limit semantics and recommended initial headroom explicit.