list_collections

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It does not explicitly state that this is a safe, read-only operation, nor does it mention any side effects, authentication needs, or rate limits. The mention of cursor-based pagination is already captured in the schema, adding no additional transparency.

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 a single, front-loaded sentence that conveys the core function and key options without any wasted words. It is compact and efficient.

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, the description covers the essential behavior: listing all collections with sorting and pagination. Since there is no output schema, the description does not explain return structure, but the term 'list' implies a collection of results, which is sufficient for most use cases. It also aligns well with the sibling tool set.

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 100%, so the baseline is 3. The description mentions sorting and pagination but does not add any meaning beyond what the schema already provides for each parameter. It does not clarify default values or parameter interactions beyond what is in 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?

The description clearly states the tool lists collections in mem.ai, which is a specific verb+resource. It also mentions optional sorting and cursor-based pagination, distinguishing it from single-collection tools like get_collection and search_collections.

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 says 'List all collections' which clearly communicates its primary use case. It does not explicitly exclude alternative tools or mention when not to use it, but the context is clear enough for an agent to select it over get_collection or search_collections.

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