List memories

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior, but the description adds crucial operational context: unchecked lines are security-checked via one Jev call and withheld if they read as AI instructions or cannot be checked. This is exactly the kind of behavioral detail an agent needs beyond structured hints.

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 compact and front-loads the core listing behavior before adding security details. The parenthetical about the Jev call is slightly dense, but no sentence is wasted.

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?

The description covers the important security filtering and default live-only behavior, and annotations handle the safety profile. However, it leaves the lone include_superseded parameter undocumented and gives no sense of the return format despite there being no output schema.

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 explain the single parameter. It only says 'live ones by default,' which implies that include_superseded exists but never names it or explains what superseded memories are or how to include them.

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 states a specific verb and resource ('List every memory in JEVMEM.md') and clarifies the default scope ('live ones by default'). It does not explicitly distinguish this from sibling tools like search_memory, but the core purpose is clear.

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 notes the default behavior of listing live memories, but gives no guidance on when to use list_memory versus search_memory or audit_memory. There are no prerequisites or exclusions stated.

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