list_memories

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'recent saved memories' but doesn't specify what 'recent' means (e.g., time frame, ordering), whether results are paginated, or any rate limits or permissions required. The description adds minimal context beyond the basic operation, leaving key behavioral traits undefined.

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 a single, efficient sentence that front-loads the core purpose ('List recent saved memories') and adds an optional feature ('optionally filtered by tag') without unnecessary details. Every word earns its place, making it highly concise and well-structured for quick understanding.

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 low complexity (2 optional parameters) and the presence of an output schema (which handles return values), the description is minimally adequate. However, with no annotations and 0% schema coverage, it lacks details on behavioral aspects like ordering, pagination, or error handling. It meets the baseline for a simple list tool but leaves gaps in usage and parameter context.

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 description coverage is 0%, so the description must compensate for undocumented parameters. It mentions optional filtering by 'tag' but doesn't explain tag semantics or format. It doesn't address the 'limit' parameter at all, leaving its purpose and constraints unclear. The description adds some meaning for 'tag' but fails to cover 'limit', resulting in incomplete parameter guidance.

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') and resource ('recent saved memories') with an optional filtering capability ('by tag'). It distinguishes from siblings like 'search_memory' by focusing on listing rather than searching, though it doesn't explicitly contrast with 'get_session' or 'list_sessions'. The purpose is specific and actionable.

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 usage for retrieving memories with optional tag filtering, but provides no explicit guidance on when to use this tool versus alternatives like 'search_memory' or 'list_sessions'. It mentions the filtering capability but doesn't clarify scenarios where listing is preferred over searching or other sibling tools.

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