mnemos_list_memories

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

With no annotations, the description must carry behavioral disclosure by itself. It does reveal that results are restricted to 'currently active' memories and that IDs are returned, but it fails to disclose the effect of the limit parameter on the 'all' claim, nor does it state ordering or pagination. 'List' implicitly signals a read-only operation.

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?

One sentence with no filler; the active verb and object are front-loaded, and the downstream use for mnemos_forget is appended without 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?

Output schema exists so return values need not be spelled out, but the single input parameter is semantically undocumented and the word 'all' conflicts with an optional limit default of 50. An agent cannot tell whether it receives every active memory or only up to the limit, making the tool incompletely specified.

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%; the sole parameter, limit, is never mentioned in the description. The agent must rely entirely on the parameter name and default value, so the description adds no meaning beyond the schema.

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?

Description opens with a specific verb and resource: 'List all currently active memories'. It further clarifies output (IDs) and intended downstream use (input to mnemos_forget), separating it from the sibling tools by its enumerating role.

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?

'For browsing or as input to mnemos_forget' gives explicit contexts in which this listing tool is appropriate. It does not explicitly say when to prefer mnemos_recall or mnemos_remember, so no exclusion is stated, but the use cases are clear enough.

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