list_memories

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

Annotations already declare readOnlyHint=true, so safety profile is clear. The description adds 'recent' as a behavioral constraint but does not explain recency criteria (e.g., time window, default ordering), nor does it describe any side effects or mutability beyond what annotations provide.

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, no extraneous words. It is front-loaded with the action and object. However, it could include a bit more context without becoming wordy; still earns its place as an efficient statement.

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?

For a read-only tool with 3 optional parameters and no output schema, the description is moderately complete. It lacks definition of 'recent' and does not indicate what fields or format the returned memories have. Given the sibling set, an AI agent might benefit from hints on pagination or sorting.

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?

Input schema covers all three parameters with descriptions, achieving 100% coverage. The description does not add any further clarification on how to use limit, agent_id, or project_id—e.g., it doesn't explain the default value of limit=100 or the behavior when agent_id is empty.

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 memories for an agent, with dashboard display context. However, among siblings like recall, export_memories, and list_episodes, it does not differentiate itself—e.g., what makes 'recent' distinct from other retrieval methods.

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 phrase 'for dashboard display' implies lightweight, UI-oriented usage, but no explicit guidance on when to use this tool versus siblings like recall (which may retrieve specific contexts) or export_memories (for bulk export). No when-not-to-use examples.

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