mempalace_search

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

No annotations are provided, so the description must reveal behavior. It states that results are verbatim content with similarity scores, and clarifies that 'context' is not used for embedding (only for future re-ranking). It also mentions cosine distance filtering, giving insight into result quality control.

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?

The description is extremely concise: two main sentences plus an important note. It is front-loaded with the key purpose ('Semantic search') and every sentence adds essential information without redundancy.

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 (6 parameters, no output schema), the description sufficiently explains the search behavior, parameter usage, and filtering. It does not cover return format details like ordering or pagination, but the core functionality is well-captured for an agent to use correctly.

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 description coverage is 100%, so baseline is 3. The description adds value by specifying 'query' max 250 chars, 'max_distance' default 1.5 and behavior when set to 0, and that 'context' is not used for embedding—information not in the schema descriptions.

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 opens with 'Semantic search' which immediately conveys the tool's core function. 'Returns verbatim drawer content with similarity scores' specifies the exact output and distinguishes it from listing or retrieval siblings like mempalace_list_drawers and mempalace_get_drawer.

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?

The description includes an IMPORTANT note clarifying how to use 'query' and 'context' parameters, and explains the max_distance threshold. It implies usage for semantic search but does not explicitly state when not to use it or compare with similar tools like mempalace_kg_query.

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