list_memories

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

Discloses ordering, memory type, and return fields. No annotations provided, so description carries full burden; lacks explicit read-only safety statement but listing implies idempotent read.

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?

Concise four sentences with front-loaded main action. Every sentence adds value with no redundancy.

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?

Covers behavior, parameters partially, and return values. Lacks explanation of 'source' parameter and potential error conditions.

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 covers 2/3 parameters with descriptions; missing parameter 'source' is not explained in description, which could clarify filtering by source.

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 the tool lists recent short-term memories from demo.memories in reverse chronological order. Differentiates itself as a time-ordered listing tool distinct from search_memories and recall.

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?

Explicitly describes use cases (review recent captures, check duplicates) and provides direct alternatives: for semantic search use search_memories, for long-term recall use recall.

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