memory_search

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

Discloses key behavior: uses embedding search, not exact keywords. No annotations provided, so description carries the burden. Does not explicitly state read-only or permissions, but search tool behavior is implied. The description sufficiently informs about the search mechanism.

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 opening sentence, followed by bullet points in the Args section. Every sentence adds value. No redundancy or filler. Front-loaded with purpose and usage guidance.

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 presence of an output schema, the description covers all necessary aspects: search method, usage policy, parameter semantics, and examples of when to use. No gaps in required information 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 coverage is 100% with descriptions for all four parameters. The description reiterates parameter details (e.g., 'in natural language' for q, defaults for project and limit). Adds marginal value beyond schema, but not significantly. Baseline of 3 is appropriate.

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?

Description clearly states 'Search shared memory by meaning' and specifies semantic (embedding) search. It distinguishes from siblings like memory_list and memory_get by emphasizing meaning-based search over keyword or ID lookup.

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 'Call this before starting work' and 'Always search before writing'. Lists concrete use cases: finding prior decisions, understanding exploration, avoiding duplication. Provides strong contextual guidance for when to invoke.

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