memo_search

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds 'Read-only with best-effort auto-capture side effects,' explaining the read-only nature and side effects, which adds value beyond annotations.

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 sentences with a third listing key parameters. Purpose is front-loaded, no redundancy. Efficient but could be slightly more structured.

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 10 parameters, the description only covers a few. Missing guidance on date filtering, limit, and other optional parameters. Output schema exists but description doesn't mention return format or pagination.

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 has 10 parameters with 0% description coverage. Description explains 'mode', 'body_chars', and 'source', but leaves 'file', 'type', 'when', 'limit', 'date_from', 'date_to' without explanation. Inadequate compensation for schema gaps.

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 it searches durable memories by text/vector similarity and mentions retrieval of source records, ids, dates, etc. However, it does not differentiate from sibling tools like memo_ask or memo_search_trace, so not a perfect 5.

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 guidance to use for direct retrieval when needing specific fields, but lacks explicit when-not-to-use or alternative comparisons to sibling tools like memo_graph or memo_history.

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