aiqbench analysis
This study demonstrates that vector RAG significantly outperforms literal tool-calling retrieval for small, dynamic knowledge bases, particularly when handling user input variations like unaccented Greek or different capitalization schemes. The research highlights that while embedding-based methods offer robustness against orthographic noise, simple prompt engineering to include the full context can nearly eliminate retrieval errors entirely. For practitioners building specialized AI assistants, this suggests that vector search is currently more resilient than strict keyword matching for real-world user interactions.
Tool-calling retrieval versus vector RAG for a small Greek--English knowledge base: accuracy and robustness to how users type Greek
arXiv:2610.08205v1 Announce Type: cross Abstract: Assistants grounded in a small, frequently edited knowledge base can retrieve through tool calls to a live data interface or through vector retrieval-augmented generation (RAG). We compare the two on KyGround, a benchmark of 198 questions drawn from the published records of a Greek--English agricultural platform on Kythera, Greece, with answers verified automatically against the records and each question posed in up to nine forms, including Greek without accents, in capitals and in three Latin-script (Greeklish) schemes. With Claude Haiku 4.5 as router and answer model, a reconstruction of the platform's tool agent answered 71.6\% of canonical Greek questions correctly and vector RAG 95.3\% (difference $-23.6$ percentage points, 95\% CI $-33.1$ to $-15.1$). Letting the router write the vector query changed nothing, and placing the whole knowledge base of about 26,000 tokens in the prompt reached 99.3\%. The tool agent's losses arose in retrieval. Its literal searches returned nothing when the router's arguments did not occur verbatim in a record, for example when it transliterated Greek into Latin script or combined words that occur in a record but not as one phrase, and the agent then abstained. Unaccented and capitalised questions cost the tool agent about 20 points and vector RAG at most 2; accent-insensitive search removed this loss, and matching stemmed tokens raised the tool agent to 83.8\% on canonical Greek. Greeklish cost both designs about 21 to 32 points. Tool interfaces for community knowledge bases need search that tolerates how users type.
Abstract:Assistants grounded in a small, frequently edited knowledge base can retrieve through tool calls to a live data interface or through vector retrieval-augmented generation (RAG). We compare the two on KyGround, a benchmark of 198 questions drawn from the published records of a Greek--English agricultural platform on Kythera, Greece, with answers verified automatically against the records and each question posed in up to nine forms, including Greek without accents, in capitals and in three Latin-script (Greeklish) schemes. With Claude Haiku 4.5 as router and answer model, a reconstruction of the platform's tool agent answered 71.6\% of canonical Greek questions correctly and vector RAG 95.3\% (difference $-23.6$ percentage points, 95\% CI $-33.1$ to $-15.1$). Letting the router write the vector query changed nothing, and placing the whole knowledge base of about 26,000 tokens in the prompt reached 99.3\%. The tool agent's losses arose in retrieval. Its literal searches returned nothing when the router's arguments did not occur verbatim in a record, for example when it transliterated Greek into Latin script or combined words that occur in a record but not as one phrase, and the agent then abstained. Unaccented and capitalised questions cost the tool agent about 20 points and vector RAG at most 2; accent-insensitive search removed this loss, and matching stemmed tokens raised the tool agent to 83.8\% on canonical Greek. Greeklish cost both designs about 21 to 32 points. Tool interfaces for community knowledge bases need search that tolerates how users type.
Computational Engineering, Finance, and Science (cs.CE); Artificial Intelligence (cs.AI)
arXiv:2610.08205 [cs.CE]
(or arXiv:2610.08205v1 [cs.CE] for this version)
https://doi.org/10.48550/arXiv.2610.08205 Focus to learn more arXiv-issued DOI via DataCite (pending registration)
results/acc_by_form.csv
results/acc_by_quote.csv
results/acc_contrasts.csv
results/acc_diagnostics.csv
results/acc_did.csv
results/acc_robustness_gaps.csv
results/acc_tool_behaviour.csv
results/ms_ablation.csv
results/ms_accuracy.csv
results/ms_contrasts.csv
results/ms_gaps.csv
results/ms_safety.csv
(8 additional files not shown) You must enabled JavaScript to view entire file list.
arXivLabs is a framework that allows collaborators to develop and share new arXiv features directly on our website.
Both individuals and organizations that work with arXivLabs have embraced and accepted our values of openness, community, excellence, and user data privacy. arXiv is committed to these values and only works with partners that adhere to them.
Have an idea for a project that will add value for arXiv's community? Learn more about arXivLabs.
Full text under the publisher's open licence · 370 words
Related coverage

Presentation: Automating the Web With MCP: Infra That Doesn’t Break
InfoQ · Jun 16, 2026

Presentation: Beyond Prompting: Context Engineering and Memory Management for AI Systems at Scale
InfoQ · Jun 10, 2026

Presentation: Beyond Prompting: Context Engineering for Production-Grade AI
InfoQ · Sep 2, 2026

[AINews] Opus 5.5 is good at explainer videos
Latent Space · Sep 29, 2026