consolidate_hipocampo

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

The description discloses the core behavior (searching, promoting, optional compression) and dry_run functionality, which is valuable given no annotations exist. However, it does not clarify whether the original episodic memories are deleted or preserved, nor the details of compression. This leaves uncertainty about side effects.

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 succinct and well-structured with a title, behavior explanation, and Args/Returns sections. Every sentence adds value, and there is no redundant information.

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 description covers the main function and parameters, and the presence of an output schema mitigates the need for detailed return info. However, it omits side effects (e.g., whether original memories are removed) and prerequisites, leaving gaps for an agent considering this mutation tool. Given its moderate complexity, it is adequate but not fully 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 description adds clear semantics for both parameters: min_age_days is 'la edad mínima en días para consolidar' with default 7, and dry_run is explained as showing only what would be consolidated. This directly supplements the schema, which has no property descriptions, making the tool usable.

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: 'migra memorias episódicas antiguas a semánticas' (migrates old episodic memories to semantic). This specific verb+resource structure distinguishes it from siblings like compress_hipocampo or set_nivel_hipocampo, which perform different operations.

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 provides no explicit guidance on when to use this tool versus alternatives like compress_hipocampo or set_nivel_hipocampo. It describes the process but lacks exclusions or preferred contexts. This leaves the agent to infer usage from the described behavior.

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