memory_get_context

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

The verb 'Get' implies a read-only operation, and 'full rendered context' hints at the output being an assembled, prompt-ready value. However, with no annotations provided, the description carries the full burden and does not explicitly state that no memory is modified, nor describe output format, size, or failure behavior.

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?

A single sentence that front-loads the action and purpose, with no filler or repetition. Every word contributes to understanding what the tool does and why it exists.

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 a simple one-parameter tool, but it leaves gaps: the role of agent_id is unexplained, the return type is only implied ('context' suggests a string but not explicitly), and there is no guidance relative to sibling memory tools. Since there is no output schema and no annotations, those omissions matter.

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 does not mention agent_id at all. It adds no meaning beyond the bare property name and type already visible in the input schema, so it fails to compensate for the complete lack of parameter documentation.

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 ('Get') and resource ('full rendered context') and clearly states the purpose ('for injection into system prompt'). This distinguishes it from sibling tools like memory_get_recent and memory_get_lane, which target narrower or different memory views.

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 'for injection into system prompt' provides a clear usage context: use this when you need the complete rendered memory context to embed into a system prompt. It does not explicitly mention when not to use it or name alternative sibling tools, so it stops short of a 5.

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