zerodb_search_memory

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It explains that the tool searches semantically and supports cross-session/filtering, but it does not explicitly state that it is read-only or describe result behaviors like ranking or return format. Some context is added, but not comprehensive.

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?

The description is two sentences, front-loaded with the primary verb and object, and contains no redundant phrasing. It efficiently communicates the core action and notable features, with clear structure.

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?

With no output schema and no annotations, the description should explain what the search returns (e.g., list of memories, relevance scores). It provides a high-level purpose but omits result format and any side-effect information. The misleading 'time range' also undermines completeness. The tool's moderate complexity is not fully addressed.

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?

The input schema covers all 7 parameters with descriptions (100% coverage), giving a baseline of 3. However, the description claims filtering by 'time range,' but no such parameter exists in the schema—only tags, user_id, session_id, scope, limit, and min_importance. This misleading statement reduces clarity and adds confusion, warranting a lower score.

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?

The description states a specific verb and resource: 'Search agent memory semantically using natural language queries.' It clearly distinguishes the tool from siblings by focusing on agent memory and cross-session capabilities, making its purpose unambiguous.

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?

The description provides clear context for when to use the tool (searching agent memory) and highlights key capabilities like cross-session search and filtering. However, it does not mention exclusions or alternatives, such as when to prefer zerodb_get_context or zerodb_semantic_search.

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