list_recent

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

With no annotations, description defines behavior (lists active memories, snippet-truncated). However, it does not disclose potential side effects, rate limits, or authentication needs, leaving gaps for an agent.

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 the purpose and provide a key behavior note. No unnecessary 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 three optional parameters, no annotations, and no sibling differentiation, the description is functional but lacks details on 'active' semantics, default behavior, and how results are ordered. Output schema exists, so return structure is covered.

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 0%, so description adds value by explaining optional filtering by type/domain. However, it does not define valid values or mention the limit parameter, so meaning is incomplete.

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?

Describes listing recent active memories with optional filters. While clear, it doesn't explicitly differentiate from sibling 'list_by_domain', which may also filter by domain but without recency emphasis.

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?

Mentions snippet truncation and points to get_memory for full records, but lacks explicit guidance on when to use this tool over siblings (e.g., list_by_domain) or prerequisites.

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