memory_episode_list

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

No annotations are provided, so the description must fully disclose behavioral traits. It states 'list episodes' but does not clarify whether the tool is read-only, whether it returns full content or metadata, or what happens with pagination (e.g., total count). This is a significant gap for a list operation.

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 concise (5 lines) and front-loaded with the main purpose. The docstring-style parameter list is clear and efficiently uses space. 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?

Given the absence of an output schema, the description should explain return values, which it does not. The tool has 4 parameters and siblings, but the description is insufficient to fully understand the tool's behavior and output.

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?

With 0% schema description coverage, the description compensates by listing parameters and adding brief explanations (e.g., 'layer: user or agent', 'Max results', 'Pagination offset'). However, it does not describe valid values beyond the defaults or the relationship between parameters (e.g., layer affects user_id).

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 'List episodes from L3 episodic memory,' identifying the specific resource (episodes) and action (list). However, it does not distinguish this tool from siblings like memory_episode_get or memory_episode_recall, which could cause confusion.

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 guidance is provided on when to use this tool versus alternatives, such as memory_episode_get for a single episode or memory_episode_recall for recall. The description lacks context on prerequisites or typical use cases.

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