memory_list

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

Declares 'pure read. Sub-millisecond.' which describes behavioral traits. Since no annotations provided, description carries full burden and does so effectively, indicating no side effects.

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?

Structured with sections: main purpose, return format, usage guidance, behavior, and parameters. Each sentence is concise and informative. 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?

Given one parameter and existence of output schema, description still provides return format details (key, tag, byte_size, last_updated) and sorting. Covers all necessary context for an agent to use the tool correctly.

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?

Explains the single parameter 'tag' with clear semantics: filter by exact tag, omit to list all. Adds meaning beyond the schema which only provides type and nullability.

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?

Clearly states verb 'List' and resource 'stored memory keys'. Distinguishes from siblings by specifying that memory_recall and memory_search are for retrieving values, not this tool. Also notes it returns metadata only.

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?

Explicit 'USE WHEN' and 'NOT FOR' sections with named alternative tools. Provides clear guidance on auditing and bulk-deletion scenarios, and what not to use it for.

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