---
title: "Comment by Mihai_LeanZero on \"AI agent tool calling: designing tools the model will actually use correctly\" | Hashnode"
description: "The errors-are-instructions section is the part I'd underline. One thing I'd add next to the \"Do not retry\" message: that text is still only a request, and a mo"
url: "https://hashnode.com/posts/ai-agent-tool-calling-designing-tools-the-model-will-actually-use-correctly/6ad0d1e8865ce90870b8c7fe/comment/6ad0dc81afbfd10d12159349"
---

[Discussion](https://hashnode.com/posts/ai-agent-tool-calling-designing-tools-the-model-will-actually-use-correctly/6ad0d1e8865ce90870b8c7fe)

Comment [AI agent tool calling: designing tools the model will actually use correctly](https://hashnode.com/posts/ai-agent-tool-calling-designing-tools-the-model-will-actually-use-correctly/6ad0d1e8865ce90870b8c7fe)

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero)

[Oct 15](https://hashnode.com/posts/ai-agent-tool-calling-designing-tools-the-model-will-actually-use-correctly/6ad0d1e8865ce90870b8c7fe/comment/6ad0dc81afbfd10d12159349)

The errors-are-instructions section is the part I'd underline. One thing I'd add next to the "Do not retry" message: that text is still only a request, and a model will occasionally retry anyway, so I'd back it with a counter in the loop that refuses a third identical call (same tool, same arguments) and returns a fixed "this exact call already failed twice" result. I'd also give the error object a retryable field of its own instead of leaving it to the prose, since a timeout and a not\_found need opposite instructions and the model shouldn't have to infer which one it got from the wording.
