Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

readOnlyHint=true already tells the agent this is a safe read-only operation. The description confirms read-only behavior and adds that search is semantic ('by meaning') and a compatibility wrapper, but it does not disclose result format, ranking behavior, limits, or how it differs behaviorally from fetch/search_thoughts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences with the purpose front-loaded and usage context second. There is no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only search tool with annotations, the definition is minimally adequate. However, there is no output schema and the description does not explain return values, ranking, limits, or sibling differentiation, leaving meaningful gaps for an agent choosing between search, fetch, and search_thoughts.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter with 100% schema description coverage, so the schema already documents the query input. The description adds only the semantic-search angle ('by meaning') and no syntax or formatting details, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: search Open Brain memories by meaning. The operation is clear, but the description does not distinguish this tool from sibling tools such as search_thoughts or fetch, which appear to overlap.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an implied usage condition: use it when ChatGPT needs search/fetch-style access to stored thoughts. However, it does not explicitly compare it with search_thoughts, fetch, or list_thoughts, nor does it state when not to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.