search_hipocampo

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

Since no annotations are provided, the description fully carries the behavioral disclosure: read-only, no side effects, no rate limits, hybrid search over technical and profile memory, and explicit return format including no-match behavior. This exceeds typical transparency.

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 well-structured with a clear opening, behavioral notes, alias note, and dedicated Args/Returns sections. Every sentence provides value, and it remains reasonably 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?

Given the tool's moderate complexity, the description covers purpose, usage, behavior, parameters, and return format. The output schema also exists, but the description still summarizes the return values, making it fully self-contained and contextually complete.

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?

The schema has 0% description coverage, but the description's Args section fully explains query as natural language text with a 500-character max and examples, and session_id as an optional filter. This adds substantial meaning beyond the schema's bare types.

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 'Busca en el Hipocampo' and elaborates 'Realiza búsqueda semántica + léxica híbrida en las bases de datos de memoria del usuario', clearly identifying the verb, resource, and scope. It also distinguishes this tool from the alias quick_hipocampo_search and other memory tools.

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 states the read-only nature and no rate limits, providing a safe-search context. It names the alternative quick_hipocampo_search for quick calls with a short name, and explains the session_id filtering condition, giving clear when-to-use guidance.

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