memo_get

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

With no annotations provided, the description carries the full burden. 'Retrieve' implies a non-mutating read operation, but it does not disclose behavior for missing IDs, return format, or any side effects. It provides basic context but lacks richer safety guarantees.

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, concise sentence that front-loads the verb and resource, with no redundant information. It earns its place and is easy to parse.

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 retrieval tool with one parameter, the description covers the core purpose but omits details about the return structure or error behavior (e.g., what happens if the ID is not found). The lack of an output schema makes this a notable gap, though the tool's simplicity mitigates it somewhat.

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 covers the sole parameter 'id' with a description and example, so schema coverage is 100%. The tool description's phrase 'by its ID' merely restates what the schema provides, adding no additional semantic meaning.

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 uses the specific verb 'Retrieve' with the resource 'previously saved conversation context' and specifies the identifier ('by its ID'). This clearly distinguishes it from siblings memo_list (lists all), memo_set (creates/updates), and memo_delete (removes).

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 implies usage when a specific memo ID is known, but it does not explicitly state when not to use it or mention alternatives like memo_list for enumerating all memos. The context is clear but lacks explicit exclusionary guidance.

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