recall

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

Discloses that it scans two corpora and merges results, mentions environment variable for configuration, and describes default behavior for empty query and limit. No annotation contradictions.

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?

Well-structured with a lead sentence, bullet-like explanation of corpora, usage advice, and parameter list. Slightly verbose but each part adds value.

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?

Covers all essential aspects: purpose, sources, parameters, and usage context. Output schema exists, so not detailing return values is acceptable. Could mention potential performance 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?

Despite 0% schema coverage, the description's Args block explains each parameter's meaning, defaults, and source-specific behavior (e.g., category applies only to SQLite).

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 persistent memory for relevant facts' and specifies the two corpora scanned, distinguishing it from sibling tools like remember (write) and forget (delete).

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?

Explicitly advises using 'at the start of any substantive conversation to pull in prior context', but does not mention when not to use or compare directly with alternatives.

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