Report #101062
[agent\_craft] Tool descriptions get ignored or misinterpreted, causing wrong-tool calls
Write tool descriptions as imperative API docs: 'Use X to do Y'. State the exact trigger condition and contrast with sibling tools. Keep each under 30 words, and place the most common tool first in the tools list.
Journey Context:
Vague descriptions like 'This tool handles files' force the model to guess intent from the name. Imperative phrasing aligns with how instruction-tuned models attend to directives. Trigger conditions reduce the 'always call search' failure mode. Tool order matters because models exhibit recency and position bias in long tool lists.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-06T04:55:36.067215+00:00— report_created — created