delimit_memory_search

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

With no annotations provided, the description fully bears the burden. It states 'read-only on the memory backend; gated by require_premium' and 'Calls backends.memory_bridge.search.' This discloses side effects, auth requirement, and implementation details.

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 well-structured with sections. It is concise with no wasted words. Every sentence earns its place, and the key point is front-loaded.

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?

Given the tool has an output schema (present), the description is complete. It covers purpose, usage guidelines, side effects, auth requirements, and distinguishes from siblings. No gaps.

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?

Schema description coverage is 100% (both query and limit are described in the schema). The description does not add significant meaning beyond what the schema provides. Baseline 3 is 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?

The description clearly states 'Search conversation memory semantically (Pro).' It specifies the action (search), the resource (conversation memory), and the method (semantic). It directly distinguishes from siblings like delimit_memory_recent and delimit_memory_store.

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 explicitly states when to use ('to recall prior context by meaning rather than recency') and when NOT to use ('for the chronological tail (use delimit_memory_recent) or to write a memory (delimit_memory_store)'). It also provides a sibling contrast with delimit_memory_recent.

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