memo_list

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds behavioral context: 'List recent memories' implying default sorting by recency, and 'Read-only' confirms the safety trait. No contradictions, and the description enriches understanding beyond annotations.

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?

Three sentences with every line earning its place: purpose, usage guidance, and parameter context. Front-loaded with the verb 'List' and resource. No filler or repetition.

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 tool's simplicity (2 optional params, full schema coverage, output schema present, and clear annotations), the description is complete. It explains the browsing workflow, the filtering behavior, and the limit cap, which is sufficient for the 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?

Schema description coverage is 100%, so baseline is 3. The description mentions '`limit` caps the number of returned records' and 'optionally filtered by memory type', but these add no new meaning beyond what is already in the input schema descriptions. No value is added to parameter understanding.

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 it lists recent memories with optional filtering by type, and explicitly differentiates it from other memo tools by positioning it as a browsing step before using get/update/delete/history tools. The verb 'List' combined with the resource 'memories' and scope is specific and unambiguous.

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 provides explicit guidance: 'Use this to browse the corpus before choosing an id for memo_get, memo_update, memo_rename, memo_delete, or history tools.' This tells the agent when to use this tool and what alternatives to use after, plus notes about the `limit` parameter.

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