Load memory

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

Annotations already confirm this is a safe, idempotent read, and the description adds meaningful behavior beyond that: default output is compact for strict MCP clients, full_content may be rejected by strict clients, and lite skips session summary bodies. No contradiction with annotations.

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?

Front-loads the core action and alternative before the extensive trigger list. The long keyword enumeration and repeated 'do not skip' warnings are useful for a critical session-start tool but make it wordier than strictly necessary.

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?

No output schema exists, but the description explains what is returned (identity, preferences, facts, session history) and how compact vs full output differs. For a zero-required-parameter read tool with rich annotations, this is complete.

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 coverage is 100%, so baseline is 3; the description adds useful context by explaining that full_content should be used sparingly and that the default output is compact. It does not add syntax beyond the schema, but it reinforces the practical meaning of the key flags.

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?

States a specific verb (loads) and concrete resources (identity, preferences, facts, recent session history) from persistent cross-session storage. Explicitly distinguishes itself from search_memory for narrow queries and clarifies the default compact output.

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?

Provides unusually explicit when-to-use guidance: immediately at session start, after context resets, when uncertain, and even when the opening message looks trivial. Also states when not to use it (pure factual lookups) and names the alternative search_memory for narrow questions.

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