Keyword Harnesses Fail Open: A Cheap Diagnostic Ladder for Tool-Use Claims in Small Language Models
Juan S. Santillana
Independent Researcher
Published October 1, 2026 · on the feed October 2, 2026 · ▲ 5 · arXiv 2610.02142
The abstract
Keyword-matching benchmarks can credit small models for tool use they never perform. We document such a false positive in a matched-architecture pair of Spanish security language models and propose a ladder of strict, cheap diagnostics. A 661.6M parameter model (approx. 65% code/technical text; no dedicated SFT) and a 1,109M model (web-heavy multi-phase curriculum; 6B-token tool-SFT) share decoder, tokenizer, and special tokens, scoring almost identically on lenient tool-use metrics (B4: 0.660 vs. 0.650). Verbatim-reproduction checks on training examples separate them completely: the 600M emits valid tool calls with generalized arguments on 6/6 examples; the 1B does so on 0/6 across checkpoints. A first-token probe localizes the 1B's failure to a missing prior (prob. 10^{-4}--10^{-5} on <|tool_call|>), which was erased by its web-heavy training phase. A targeted SFT recipe (diverse corpus, 5x higher learning rate, 2,202 steps, ~3.3 GPU-hours) repairs the 1B using three orders of magnitude fewer tokens than the failed phase. On all 269 corpus rows, valid emission rises from 0.100 to 0.959 (600M: 0.926). On 238 unseen prompts, the repaired 1B passes 0.536 vs. the 600M's 0.428 (p = 0.004). Embedding-drift checks show the repair did not move the trigger token's tied embedding (97.7% of the bf16 table remains bit-identical), meaning changes live in the surrounding network. Both models over-trigger, rarely answering negative prompts without a call (0.09 for 600M, 0.17 for repaired 1B). Factorial analyses confirm all repair configurations install the format, though suppression benefits from a diverse corpus remain a hypothesis due to seed sensitivity. This cheap diagnostic ladder costs minutes of CPU time and should gate tool-use claims on small models.
The Brief
3:00A short podcast summary of the paper. Written and voiced by AI.
Transcript
Keyword Harnesses Fail Open. A Cheap Diagnostic Ladder for Tool-Use Claims in Small Language Models. By Juan S. Santillana, working independently. Published on the first of October. No code repository is linked to it.
Keyword-matching benchmarks can give a small model credit for tool use it never actually performs. The paper documents one such false positive and proposes a ladder of diagnostics that are strict and cheap enough to catch it. The case is a matched-architecture pair of Spanish security language models. They share a decoder, a tokenizer and special tokens, and on lenient tool-use metrics they score almost identically: zero point six six zero against zero point six five zero on the measure called B4.
Their histories differ. The smaller model has six hundred sixty-one point six million parameters, was trained on roughly sixty-five percent code and technical text, and had no dedicated supervised fine-tuning. The larger, at about one point one billion, went through a web-heavy multi-phase curriculum followed by six billion tokens of tool-focused fine-tuning.
The first rung of the ladder is a verbatim-reproduction check on training examples, and it separates the two completely. The six hundred million model emits valid tool calls with generalised arguments on six of six examples. The one billion model does so on none of six, across checkpoints. A first-token probe then localises the failure to a missing prior: the larger model puts probability between ten to the minus four and ten to the minus five on the tool call token, a prior erased by its web-heavy training phase.
A targeted fine-tuning recipe repairs it, with a diverse corpus, a five times higher learning rate, two thousand two hundred and two steps and about three point three GPU-hours. That is three orders of magnitude fewer tokens than the phase that failed. Across all two hundred and sixty-nine corpus rows, valid emission rises from zero point one to zero point nine five nine. On two hundred and thirty-eight unseen prompts, the repaired model passes zero point five three six of the time against the smaller model's zero point four two eight, with a p-value of zero point zero zero four.
Embedding-drift checks show the repair left the trigger token's tied embedding where it was. Ninety-seven point seven percent of the bf16 table stays bit-identical, so the changes live in the surrounding network.
Several limits are stated plainly. Both models over-trigger, rarely answering a negative prompt without making a call: zero point zero nine of the time for the smaller model and zero point one seven for the repaired one. Factorial analyses confirm that every repair configuration installs the format, but the idea that a diverse corpus helps suppress unwanted calls stays a hypothesis, because the results are sensitive to the random seed. And the evidence comes from a single matched pair of small models.
Two models that a lenient harness scores as equals turn out to sit at opposite ends: one calls tools, the other almost never could. The ladder that exposes this costs minutes of CPU time, and the author's position is that checks of this kind should gate any tool-use claim made about a small model.
Paper Quest · 7 chapters · about 41 min
Play this paper
Learn it by doing: make the calls the authors made, guess the result before you see it, and defend it in a viva graded on your own words. Chapter 1 is right here.
Chapter 1 🧩 · The problem
Two models, one score. Only one can actually call a tool.
You are comparing two small Spanish security language models that share a decoder, tokenizer and special tokens. A keyword-matching benchmark gives them almost the same tool-use score.
The road ahead
- 1 · The problem ~7 min Two near-identical small models get almost the same tool-use score, but a keyword benchmark cannot tell whether either one really makes tool calls.
- 2 · What came before ~3 min
- 3 · The key idea ~9 min Replace the lenient keyword score with strict, cheap checks that demand real calls, locate why one model fails, then repair it with a short targeted fine-tune.
- 4 · Choose your own research ~3 min
- 5 · Build the method ~8 min Check for real calls on training examples, probe the call-start token, repair with a targeted fine-tune, then test the repaired model on unseen prompts.
- 6 · The experiment ~6 min You’ll guess: On unseen prompts, did the repaired 1B model beat the 600M model that had emitted tool calls by default?
- 7 · The viva ~5 min Three questions from the examiners, answered in your own words. Win it for the paper’s trophy.
Free, with Google or an email address. Your stars and progress are kept.