retrieve_from_memory

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

With no annotations provided, the description carries the full burden. It indicates a read-only search but does not explicitly state it is safe, non-destructive, or mention any authentication or side effects. The return format (success, entries, count) is mentioned but not behavioral traits.

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 very concise with a clear front-loaded purpose statement followed by a parameter list. Every sentence serves a purpose, though it lacks usage guidelines.

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 presence of an output schema (not shown), the description need not detail return values further. It covers the main purpose, parameters, and return structure. However, it is incomplete regarding behavioral context and the inconsistency in caller_agent_id requirement.

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 brief meaning to parameters (query, tags, limit, caller_agent_id) beyond the schema's empty descriptions. However, it incorrectly marks caller_agent_id as required, contradicting the schema (schema shows it as optional with default null). The limit default is correctly implied but not stated.

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 it retrieves knowledge from memory, using the verb 'retrieve' and resource 'memory'. It distinguishes from siblings like 'save_to_memory' and 'delete_memory_entry' but lacks differentiation from 'retrieve_from_global_memory' or 'search_memory_archive'.

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?

No explicit guidance on when to use this tool versus alternatives. While siblings imply different operations, there is no statement of when to choose retrieve over get_memory_entry or list_memory_entries.

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