A tool's wording and defaults decide how wide the agent searches
Agents follow tool descriptions literally, including the loose parts.
SymptomAn agent searches wider than the question needs, beyond the account it names or back past the period it asks about.
A search tool's description tells the agent how to use it, so a line meant as a possibility, such as "you can also look at nearby items", reads to an agent as an instruction.
Agents take such lines as the default. They mix raw sources into searches that facts would answer, and widen scope beyond the account the question names.
Similarity search alone has no sense of time, so a phrase like last quarter becomes words to match instead of a date bound.
Results need to say what they are, too. An unlabelled near miss can do real damage, because an agent given only similar-name hits can conclude that an account it was asked about doesn't exist.
Read the 20 most recent search-tool calls in your agent's transcripts. Count how many calls omit the account scope or mix raw sources with facts. More than 2 of 20 means the tool's defaults decide the width instead of the question.
Passes if18 or more of 20 sampled search-tool calls carry an account scope. The same calls carry only the source type the question asked for.
Access needed:agent-transcriptslocal-config
- 01Make the narrowest source type the default and wider sources an opt-in.
- 02Require the account scope on every call when the question names an account.
- 03Turn relative time in the question, such as last quarter, into explicit date bounds before searching.
- 04Label each hit with how it matched. Say when a hit is only a similar name.
- 05Reread every tool description for phrases an agent could take as a default.