Quick answer
Quick answer: back up the original, pick the right format/settings, run a small batch, spot-check the output. Tool schemas/results consume tokens; do not attach too many tools.
Why it matters
Get the shortest path working before optimizing.
Longer descriptions cost more.
Step by step
- Confirm the model context and output budget.
- Paste the prompt/document and estimate tokens/usage.
- Above 80-90%, split, summarize or retrieve.
- Count system prompts/tool schemas too.
- Verify billing/hard limits with the official tokenizer.
Common mistakes
- Treating character count as token count.
- Ignoring output/system prompt usage.
- Assuming all models use the same tokenizer.
- Stuffing a long document instead of retrieving/summarizing.
Checklist
- Model context confirmed.
- Output budget reserved.
- System/tool prompts counted.
- Long text retrieved/split.
- Critical cases checked with the official tokenizer.
Key facts
- Longer descriptions cost more.
- Truncate/summarize results.
FAQ
What is the quick answer for Tool calling?
Quick answer: back up the original, pick the right format/settings, run a small batch, spot-check the output. Tool schemas/results consume tokens; do not attach too many tools.
How long does it take?
Usually 1-3 minutes; for intermittent issues, run 30 seconds and retest elsewhere.
Is data uploaded?
Runs locally and does not upload video/audio; extensions may still read the page.
Source: OpenAI function calling