listMemories

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

Annotations already provide readOnlyHint=true and idempotentHint=true. The description adds 'Read-only; no side effects' but this is redundant with annotations. It adds value by noting the result 'can be very large,' which is useful behavioral context. Overall moderate contribution 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?

The description is highly concise: two sentences in the first paragraph followed by clear 'WHEN TO CALL' and 'WHEN NOT TO CALL' sections. Every sentence serves a purpose with no waste.

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 read-only list tool with no parameters and no output schema, the description is complete. It covers the purpose, usage guidelines, behavioral traits, and constraints (unfiltered, potentially large).

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?

There are zero parameters, so schema coverage is 100% trivially. The description implicitly conveys no inputs by stating it returns everything. For zero-parameter tools, the baseline is 4, and the description meets this without needing extra detail.

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 'Return every memory stored for the current project, unfiltered and without ranking.' This is a specific verb ('Return') and resource ('every memory') with scope ('unfiltered'), and it distinguishes from the sibling 'retrieveMemories' which ranks by relevance.

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 includes explicit 'WHEN TO CALL' and 'WHEN NOT TO CALL' sections, providing clear context for when to use this tool (inventory, audit, duplicates) and when to use the alternative 'retrieveMemories' (normal session start).

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