delimit_memory_search

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

The description mentions 'Pro', indicating a license requirement, which is a behavioral constraint. However, it does not disclose whether the operation is read-only, how search results are ranked, or any side effects. With no annotations, more detail would be beneficial.

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?

A single sentence clearly captures the tool's action and scope. No unnecessary words, and the key information 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 existence of an output schema, the description does not need to explain return values. However, it lacks context about when to use this tool versus memory siblings and does not mention pagination or result ordering. It is minimally complete.

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 has 100% description coverage for both parameters, so the schema already explains them well. The description adds nothing beyond what the schema provides, meeting the baseline.

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 the tool searches conversation memory semantically, which distinguishes it from 'delimit_memory_recent' and 'delimit_memory_store'. However, it does not explicitly differentiate from siblings or expand on what 'semantically' means.

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?

No guidance is given on when to use this tool instead of memory alternatives like 'delimit_memory_recent' or 'delimit_memory_store'. The description only implies usage through the name.

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