rememb_search

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

With no annotations, the description declares it as a safe, read-only operation with no side effects, and explains semantic similarity ranking. It could mention result format or pagination, but overall transparency is good.

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?

Three sentences efficiently cover purpose, safety, usage guidance, and result ranking. Front-loaded with main action; no unnecessary words.

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?

For a search tool with 6 parameters and no output schema, the description adequately explains the main behavior and parameter interactions. Could elaborate on return structure, but completeness is sufficient.

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 coverage is 100% (all 6 parameters have descriptions). The description adds value by explaining semantic similarity, 'top_k most relevant results', and that tag filter applies before semantic search, going beyond schema basics.

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 memory entries by content or tags using semantic similarity, and distinguishes it from siblings like rememb_read (loading all entries) by focusing on specific topic finding.

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 this tool instead of rememb_read when seeking specific entries by topic, providing clear context. However, it does not elaborate on when not to use it or other alternatives among the 12 siblings.

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