recall

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

No annotations are provided, so the description must carry behavioral disclosure. It explains search modes and optional query behavior but does not mention read-only versus mutation side effects, authentication requirements, or rate limits. For a read-only search tool, the description is adequate but not exhaustive.

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, extremely efficient, and front-loaded with the core action and supported features. Every sentence earns its place with no redundancy.

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 no output schema, the description focuses on usage and filtering capabilities without detailing return format. However, for a search tool with 0 required parameters and nested objects, the description sufficiently covers behaviors like optional query and server mode selection.

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%, so the baseline is 3. The description lists key parameters (mode, tags, limit, query, timeRange, minImportance) and their purpose, adding value beyond the schema by summarizing the feature set. It does not add extra syntax details for nested parameters like timeRange.

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 performs 'Search and retrieve memories,' a specific verb-resource pair. It distinguishes the tool from siblings like 'search' and 'fetch' by specifying memory-specific search modes (keyword/semantic/hybrid) and specialized filters (tags, time, importance).

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 on when to use the tool (for memory search and retrieval) and highlights flexibility with optional query for filters-only searches. However, it does not explicitly exclude scenarios when a sibling like 'search' or 'fetch' would be more appropriate.

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