list_memories

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

With no annotations provided, the description must disclose behavioral traits. It only mentions 'recent' without defining recency, and does not state whether the operation is read-only, destructive, or requires authentication. No behavioral context beyond listing memories.

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 short and to the point, but it sacrifices crucial details for brevity. While it avoids fluff, it omits important information about usage and behavior, making it less helpful than it could be.

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 tool's simplicity (2 parameters, no output schema, no annotations), the description should fully cover its behavior. It fails to define 'recent', explain pagination, ordering, or response format. Considering the presence of many sibling tools, more context is needed for correct selection.

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 limited value over the schema: it confirms optional filtering by type, which aligns with the 'memory_type' parameter. However, it does not explain the 'limit' parameter, and the schema already describes memory_type's allowed values. Schema coverage is 50%, and the description fails to compensate for the missing description of 'limit'.

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 states 'List recent memories', which clearly indicates the verb (list) and resource (memories). It also mentions optional filtering by type, which provides additional specificity. However, it does not explicitly distinguish from sibling tools like 'search_memory' or 'consolidate', leaving some ambiguity.

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 no guidance on when to use this tool versus its siblings (e.g., search_memory, consolidates). It does not mention prerequisites, limitations, or alternatives. The context is implied but not explicit.

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