memoryos_get_memory_history

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

With no annotations, the description must carry all behavioral information. It explicitly uses 'Fetch' to indicate a read-only operation and 'append-only' to signal that the history cannot be altered, providing transparency about 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?

The description is a single, compact sentence with no extraneous words. It effectively communicates the core function in the fewest possible terms.

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?

The description is adequate for the tool's simple role, but it does not mention return shape, ordering, pagination, or error conditions. Since there is no output schema, a bit more detail about the expected response would round it out, though the core function is clear.

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?

The schema provides only a required memory_id with no description, and the tool description offers minimal additional context—merely tying the ID to 'a memory.' It does not explain the format, source, or validation of the ID, leaving the parameter semantics largely to inference.

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 the action (Fetch) and the resource (append-only version history for a memory). It distinguishes from get_memory (current state) and list_memories (all memories) by focusing on historical versions.

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?

It provides clear context that this is for retrieving historical versions, indicating a distinct use case from the other memory-fetching tools. However, it does not explicitly name sibling tools or state when not to use this tool, so it stops short of full explicitness.

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