search_memories

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does not mention whether the search is read-only, how results are ordered, or any side effects. The phrase 'semantic vector search' describes method but not behavior like return format or pagination.

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?

One sentence with no redundancy. It is appropriately concise, though it sacrifices substance. The structure is a simple declarative statement, which is efficient but lacks any preparatory or explanatory context.

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?

The tool is complex (5 parameters, no output schema, no annotations), but the description provides minimal context. It does not explain the return format, threshold semantics, or how memory_type filters results. This is inadequate for an agent to invoke the tool confidently.

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 only 20% (only 'query' has a description). The tool description adds no details about 'tags', 'limit', 'threshold', or 'memory_type'. With this low coverage, the description must compensate but does not, leaving most parameters undefined.

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's function: 'Search through memories' with the specific method 'semantic vector search'. The verb + resource is specific, and the semantic vector search differentiates it from the sibling tool list_memories, which likely returns all memories.

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 gives no guidance on when to use this tool versus alternatives like list_memories. There is no mention of appropriate scenarios, exclusions, or preferred conditions. The usage context is only implied by the phrase 'Search through memories'.

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