search_hipocampo

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

The description explains the search scope (technical memory and profile items) and clarifies the return format (plain text, with indication if no results). However, it does not state that the tool is read-only, mention any rate limits, or disclose potential side effects. Since no annotations are provided, the description carries the full burden but leaves some behavioral aspects implicit.

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 line, followed by details in paragraphs and examples. It is concise enough for its content, but the examples could be shortened without losing clarity.

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?

For a search tool with one parameter and an output schema, the description covers the essentials: what is searched, how, and what results look like. However, it lacks information on typical response size, pagination, or any filtering capabilities that might be relevant given the complexity of hybrid search.

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% coverage, so the description must clarify the parameter. It provides useful examples of valid queries, which helps the agent understand the expected input. However, it does not specify length limits, encoding, or precise formatting requirements.

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 that the tool performs hybrid semantic and lexical search in the Hipocampo memory system, including technical and profile databases. It provides specific examples of queries. However, compared to the sibling 'quick_hipocampo_search', it does not explicitly highlight the difference in scope or speed.

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 examples of queries but offers no guidance on when to use this tool versus alternatives like 'quick_hipocampo_search'. There is no mention of prerequisites, limitations, or recommended use cases.

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