getMemory

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

Describes read-only nature and no side effects, consistent with annotations. Adds value by specifying the record fields returned, beyond the annotations that only indicate readOnlyHint and idempotentHint.

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?

Extremely concise, with clear sections on purpose, when to call, and when not to call. No redundant sentences.

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?

Despite no output schema, the description fully explains the return value content. For a simple single-record fetch tool, this is complete given the annotations and schema.

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 coverage is 100%, and the description adds meaningful context: 'Exact UUID of the memory to fetch. Obtain from a prior retrieveMemories or listMemories result.' This clarifies the expected source of the parameter.

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 it fetches a single memory record by exact ID, lists returned fields (content, kind, importance, timestamps, session metadata), and distinguishes from sibling tools like retrieveMemories.

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?

Explicitly provides when to call (when you have a memoryId from prior results) and when not to call (for topic-based search, use retrieveMemories instead).

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