get_memory

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

With no annotations provided, the description must disclose safety and behavioral traits. It only says 'Retrieve', which implies read-only but does not explicitly state that it has no side effects, what happens if the memory does not exist, or return format. This is a significant gap for a tool with no annotation support.

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 clear sentence, directly stating the action and the key parameters. It is efficient and easy to parse, with no redundant information.

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?

Given no output schema and no annotations, the description should at least mention return value or error behavior. It covers the basic purpose but lacks information about what the tool returns on success or failure, which is important for a retrieval operation. As a simple tool, it is minimally viable but incomplete.

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%, so the description must compensate. It mentions 'by category and name' but adds no extra meaning beyond rephrasing the schema property names. No details on format, constraints, or how these parameters are used in the lookup.

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 a specific verb 'Retrieve' and identifies the resource 'memory' with scope 'specific memory by category and name'. This clearly distinguishes the tool from siblings like list_memories (which lists) and add/delete_memory (which modify).

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 'specific memory' implies this is for fetching a single, known memory rather than listing all, providing clear context for use. However, it does not explicitly state when not to use it or name list_memories as an alternative, so a small deduction applies.

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