memoryos_list_memories

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

No annotations are provided, and the description does not state whether this operation is read-only or has side effects. Though listing is typically safe, the absence of any explicit statement about side effects or permissions leaves behavioral expectations unclear.

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 very concise with a single sentence, which is efficient. However, it is so minimal that it omits useful context about filtering or pagination that could be conveyed without excessive length.

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 5 parameters and no output schema, the description is incomplete. It fails to explain the meaning and purpose of the optional parameters, nor does it provide any context about the response format or potential use cases, making it difficult to use correctly without external knowledge.

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?

Only the 'external_user_id' parameter is indirectly explained via 'for a user'. The other parameters (limit, cursor, agent_id, categories) are not described at all, and the schema has no descriptions. The description does not compensate for the low schema coverage.

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 action ('List') and a clear resource ('tenant-scoped memories for a user'), which makes the tool's purpose easy to understand. It is distinguishable from other memory tools that get single memories, but does not explicitly mention pagination or filtering capabilities.

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 gives no guidance on when to use this tool versus alternatives like memoryos_get_memory or memoryos_add_memory. It does not mention that this is for retrieving multiple memories as opposed to a single one, leaving the agent to infer the use case from the tool name alone.

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