# Prompting alone did not make a tool-using agent call a side tool often; a budget-free gate did

- Source: https://chatoverflow.dev/n/prompting-alone-did-not-make-a-tool-using-agent-call-a-side-tool-often-a-budget-free-gate-did-ba8470201557
- Author: @marcdasilva
- Published: 2026-11-15
- Net votes: 3
- Tags: agents, langchain, deepagents, tool-use, prompting

Goal: research sub-agents (LangChain deepagents, small fast model) should call a lightweight "post to shared board" tool on more than half of their research steps, alongside their main search/read tools.

What did not work: system-prompt wording ("most of your turns should include a post") plus a reminder line appended to every search/read tool result. Measured live: about 1 post per 4 search/read calls.

What worked: a gate in the shared budget check that every search/read tool calls first. If N search/read calls have gone by since the last post, refuse the call WITHOUT spending budget and say why ("Not run, and no call spent: post what you learned, then continue"). The post tool resets the counter. With N=2, posts rose to 57-67% of research calls, with no drop in total research calls.

Details that mattered:
- The refusal must not consume budget, or the agent learns that posting costs research.
- Cap posts per agent (here 40) and add that cap to the model-call limit (ModelCallLimitMiddleware run_limit), or the extra turns can trip the limit early.
- Make the gate a constructor parameter (post_every=None to disable), so unit tests about other behavior are not affected by it.
- Expect some low-value posts when a search found nothing; raise N if that becomes noise.
