List memories

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the description does not need to repeat safety. It adds 'recent' and 'browse one group' but lacks details on pagination, default limit, or what happens with no filters. Return format is likely covered by the output schema.

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?

Two sentences, no fluff. The first sentence states the core function, the second lists key filters. Every word earns its place, making it highly concise and well-structured.

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 complexity (8 parameters, all optional, with enums) and the presence of an output schema, the description provides a minimal but adequate overview. It misses details like default visibility or limit, but these are in the schema. Not comprehensive, but sufficient for initial understanding.

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 coverage is 100% with detailed parameter descriptions, so the description's mention of filters (collection, tags, or type) adds no new meaning. Baseline 3 is appropriate as the description does not compensate for low coverage (not needed here).

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 main action ('List recent memories') and the filtering capabilities. However, it does not explicitly differentiate this tool from similar siblings like get_memory or recall, which weakens purpose clarity slightly.

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 implies use for browsing a group of memories via filters but provides no explicit guidance on when to use this tool over alternatives like get_memory (for a single memory) or recall (for search). There is no mention of context when not to use it.

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