memory_episode_recall

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

No annotations provided. Description indicates a read operation but does not disclose ordering, pagination, or behavior when tag is empty. Lacks context beyond basic action.

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?

Short and to the point, with clear parameter listing. No extraneous text, but could be more structured (e.g., separate parameter descriptions).

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?

No output schema, so description should mention return format, which it does not. With 4 optional parameters and no sibling differentiation, it is adequate but incomplete for full context.

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 0%. Description adds basic explanations for all 4 parameters (layer, user_id, tag, limit) but lacks detail (e.g., valid values for layer, meaning of 'User Id'). Sufficient but minimal.

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?

Clearly states verb 'Recall' and resource 'episodes', with optional tag filter. Distinguishes from memory_episode_get (likely single episode) and memory_episode_list (possibly all episodes) by implying filtered retrieval, though not explicitly stated.

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?

Implies use when recalling episodes with optional tag filter, but no explicit guidance on when to use versus alternatives like memory_episode_get or memory_recall. No exclusions or best practices mentioned.

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