FindingcurrentRunning agents

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.

Check your setup read-only

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

If it fails: changes to make later (not part of the check)
  1. 01Make the narrowest source type the default and wider sources an opt-in.
  2. 02Require the account scope on every call when the question names an account.
  3. 03Turn relative time in the question, such as last quarter, into explicit date bounds before searching.
  4. 04Label each hit with how it matched. Say when a hit is only a similar name.
  5. 05Reread every tool description for phrases an agent could take as a default.
Applies ifYour agent answers account questions for sellers through a search tool that can span accounts or mix raw sources with extracted facts.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.