memory_search

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

No annotations provided; description states it searches keys and values, implying read-only, but doesn't disclose effects, performance, or authorization needs.

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?

Concise with purpose first, then parameter list. No extra fluff, though could be more compact.

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?

Covers all parameters and basic behavior, but lacks description of return format or pagination for limit.

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?

Description adds meaning to each parameter (query, namespace, tags, limit) beyond the schema, which only has titles.

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?

Clear verb 'durchsuchen' with resource 'Memories', and distinguishes from sibling tools like memory_delete or memory_retrieve by explicitly stating it searches keys and values.

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?

Implies usage for searching memories with optional filters, but no explicit when-to-use vs alternatives like memory_retrieve or memory_list.

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