list_memories

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds minimal behavioral context beyond stating 'List stored memories,' which is consistent. It does not discuss side effects, rate limits, or pagination, but given the annotations, the bar is met at a basic level.

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 concise and well-structured, with a clear purpose statement, an Args section, and a Returns line. Every sentence adds value, no 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?

For a simple list tool with two optional parameters and an output schema, the description adequately covers usage and return format. However, it omits details like whether results are ordered, pagination behavior, or limitations (e.g., maximum limit). Still, it is largely complete given the tool's complexity.

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 compensate. It explains both parameters: 'limit' (maximum number, default 50) and 'tags' (optional filter). This adds meaningful semantics beyond the bare schema, though it could specify the tag format (e.g., comma-separated).

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 clearly states 'List stored memories with optional tag filtering,' which uses a specific verb ('List') and resource ('stored memories'). It distinguishes the tool from siblings like 'list_agents' or 'list_capabilities' by specifying the resource type and the optional filtering capability.

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 does not provide explicit guidance on when to use this tool versus alternatives. There is no mention of when to use 'list_memories' instead of related tools like 'remember' or 'draft_memory', nor any context about prerequisites or limitations.

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