Fetch a memory

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

Annotations already declare readOnlyHint=true, so the description does not need to restate safety. The description adds only the id-based retrieval behavior and provides no extra context about error handling or side effects, which is acceptable for a simple read but adds no depth beyond the annotation.

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 focused sentence with no filler. The key information, fetch by id, is front-loaded and every word earns its place.

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 one-parameter read-only tool with an output schema, the description is largely sufficient for correct invocation. The main gap is that it does not explicitly guide the agent toward this tool relative to memory_search or memory_recent, but the simple signature and 'by id' phrasing cover the essentials.

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 0%, and the description only says 'by id,' loosely mapping record_id to a memory identifier. The single parameter is self-explanatory, so the lack of detailed semantics is not severe, but the description does not provide format, source, or usage guidance for record_id.

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 'Fetch one memory by id' names a specific verb, resource, and identifying method. This clearly distinguishes memory_get from siblings like memory_search and memory_recent, which retrieve memories by other criteria.

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 phrase 'by id' implies this tool is appropriate when the caller knows a specific memory identifier. However, it does not explicitly say when to use this tool instead of memory_search, memory_recent, or other sibling tools, nor does it provide exclusions.

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