memory_context

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

No annotations present, so description carries full weight. It discloses that every pull is logged as a signed receipt, but lacks details on performance implications, rate limits, or authorization needs. Acceptable but not comprehensive.

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?

Two sentences with no wasted words. First defines the tool's result, second gives usage guidance, third a behavioral note. Efficient and front-loaded.

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?

Despite no output schema, the description enumerates return contents (entities, observations, relationships, preferences) and mentions logging. Adequate for a straightforward context dump tool. Some missing details on ordering or format, but overall sufficient.

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 covers all four parameters with descriptions (100% coverage). The description adds no additional parameter meaning beyond what the schema already provides, so baseline score applies.

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 tool retrieves a 'complete context dump' of memories, listing specific components (entities, observations, relationships, preferences). It distinguishes from sibling tools like 'memory_entities' (which focuses on entities only) by being a comprehensive snapshot.

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?

Explicitly recommends calling at conversation start to understand what's known, providing clear context. Does not explicitly exclude alternative tools but implies this is for full context, not filtered queries.

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