agent.memory.list

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

With no annotations, the description carries the full burden. It discloses key behaviors: returns metadata only (no values), cursor-paginated ordering, optional prefix filter. It does not cover authentication, rate limits, or side effects, but as a read operation this is acceptable.

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 concise sentences front-load core purpose and ordering, then quickly cover pagination, filter, and guidance to sibling tool. No wasted words.

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 no output schema, the description explains that it returns metadata and directs to another tool for values. It could be more explicit about the response fields (e.g., keys with updatedAt), but for a list tool with three parameters, it is reasonably complete.

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 67% with descriptions for all three parameters. The tool description adds 'newest-first by updatedAt' which contextualizes the order but does not elaborate on parameter semantics beyond what the schema provides. Baseline 3 is appropriate.

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 verb 'list', the resource 'keys in memory namespace', the ordering 'newest-first by updatedAt', pagination method 'cursor-paginated', and an optional prefix filter. It distinguishes from siblings like agent.memory.get (fetch values) and agent.memory.put (store).

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 provides clear context for usage: it returns metadata only and directs to agent.memory.get for values. It implies when to use (listing keys) but does not explicitly list exclusions or prerequisites. The mention of an alternative tool enhances guidance.

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