memory_store_list

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

With no annotations, the description carries full burden. It discloses listing behavior, pagination support, and warns of destructive consequences if wrong store is attached. However, it does not explicitly state read-only nature.

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?

Triple-sentence description is concise, front-loads purpose, and adds critical context without wasted words. Every sentence earns its place.

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 presence of output schema (handles return values), the description covers listing, pagination, and usage context fully. Warnings about store attachment provide necessary completeness for safe use.

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 has 2 optional parameters (limit, page) with 0% coverage. Description mentions pagination via 'next_page' but does not explain limit or parameter types. Partially compensates but lacks full parameter documentation.

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 the verb 'List' and resource 'memory stores', and specifies the output format (summaries with id, name, description, metadata). It distinguishes from sibling 'memory_store_get' (single store retrieval) and other listing tools.

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?

Provides explicit when-to-use guidance: identifies memory stores as agent's persistent memory, explains how to attach the correct store via session_start, warns about consequences of using wrong store, and hints at pagination via next_page.

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