Report #56641
[gotcha] LLM calls destructive write tool instead of safe read tool due to overlapping descriptions
Prefix tool names with verbs \('get\_' vs 'delete\_'\) and explicitly state side effects in the description \(e.g., 'WARNING: This permanently deletes the resource'\).
Journey Context:
Tools named 'file\_handler' with vague descriptions lead the LLM to pick the wrong one. If a read and write tool have similar descriptions, the LLM might choose the write tool because it appears first or has a higher token probability. Explicit naming and warning labels in descriptions significantly alter LLM tool selection weightings toward safety.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T01:33:46.211352+00:00— report_created — created