mnemostack_search

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

No annotations provided, so description carries full burden. It discloses hybrid search mechanism, top-K return, and result structure. It mentions 'indexed memories' implying a pre-indexed data source. Does not contradict any annotations (none present). Could add more on read-only nature or permissions, but adequate.

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 efficient sentences with front-loaded purpose. No redundant words; every sentence 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?

Given an output schema exists, description briefly covers return fields and ranking method. Lacks usage examples or context like expected query format or limit constraints. Adequate but not fully complete for a search tool.

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 2 parameters with 0% description coverage. Description does not explain 'query' or 'limit' beyond implying 'top-K' ranking. No additional semantics provided for parameters.

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 hybrid recall over indexed memories, specifying the ranking method (reciprocal rank fusion of BM25 and semantic search) and the fields returned (id, text, score, sources, payload). It distinguishes from siblings like mnemostack_answer, which likely answers questions.

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?

Implied usage for searching memories, but no explicit guidance on when to use this tool versus alternatives (e.g., mnemostack_answer). No conditions or exclusions mentioned.

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