memory_search

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

Discloses semantic embedding search behavior and the effect of max_content_length on results. Annotations already indicate read-only and non-destructive nature; the description adds valuable context beyond annotations without contradiction.

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 clear purpose line, then usage guidance, then parameter list. Every sentence provides value, concise without redundancy. Front-loaded with key information.

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 the tool's complexity (5 parameters, output schema exists), the description covers all aspects: purpose, search mechanism, usage recommendations, parameter details, and return value truncation. No gaps detected.

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%, so baseline is 3. The description adds extra context for each parameter, such as 'defaults to MCP_PROJECT if set' for project and the purpose of max_content_length, improving clarity beyond the schema.

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 shared memory by meaning' with a specific verb and resource. It distinguishes from keyword search by mentioning semantic embedding, and implicitly differentiates from sibling tools like memory_get and memory_list.

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 to call before starting work and always search before writing. Provides examples of when to use (finding prior decisions, avoiding duplication). Lacks explicit when-not-to-use or alternatives, but the guidance is clear and actionable.

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