memo_get

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, but the description adds valuable behavioral context: the read-only nature, the ambiguity error, and the MEMO_EMITTED_LEDGER recovery counting. It goes beyond the structured safety hints without contradicting them.

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 front-loaded with the core purpose, then gives edge cases and usage guidance. The final paragraph about MEMO_EMITTED_LEDGER is detailed and possibly overlong, but it is relevant to behavioral transparency and does not repeat structural data.

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 tool has a simple schema, rich annotations, and an output schema. The description covers purpose, edge cases (None, ambiguity), alternatives, and advanced ledger behavior, leaving no significant gaps for an agent to invoke it 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?

The schema already provides 100% coverage for the single 'id' parameter, including the format ('Full 32-char memory id or a unique prefix'). The description does not add meaning beyond the schema; it reinforces the same idea but does not introduce new semantic details.

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 opens with a specific verb and resource: 'Fetch one memory by id or unique id prefix.' It clearly distinguishes from sibling tools like memo_search and memo_list by focusing on retrieval by identifier, and it explicitly states the possible return outcomes (full record, None, ambiguity error).

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 explicitly states when to use alternatives: 'Use memo_search or memo_list first when you do not know the id.' This gives clear contextual guidance for choosing the right tool and when not to use memo_get.

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