Restore operational context by loading a named session. Returns stored key-value entries with timestamps to pick up where you left off.
Load a previously saved session by name. Returns all stored key-value entries with timestamps. Use at the start of a session to restore context from a previous conversation.
| Name | Required | Description | Default |
|---|---|---|---|
| session | Yes | Session name to load |
Changes observed during successful MCP inspections.
v2.9.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must disclose behavior. It confirms load is read-only by stating 'Load' and 'Returns' without mentioning side effects. However, it does not clarify if loading activates the session or causes any internal state changes beyond retrieval, leaving some ambiguity.
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: first defines purpose and output, second provides usage guidance. No wasted words, front-loaded with essential information. Perfectly concise and well-structured.
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?
Tool has no output schema, so description must compensate. It states 'Returns all stored key-value entries with timestamps' but lacks specifics on format, structure, or error handling (e.g., session not found). Coverage is adequate for basic understanding but not fully complete given the absence of schema.
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% and parameter 'session' is already described as 'Session name to load' in the schema. Description adds minimal extra meaning ('by name' and context hint). Baseline score of 3 is appropriate as schema does the heavy lifting.
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?
Description clearly states 'Load a previously saved session by name' and specifies output 'Returns all stored key-value entries with timestamps'. The verb 'load' combined with resource 'session' is specific, and the usage hint distinguishes it from siblings like save_session, delete_session, and list_sessions.
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 advises 'Use at the start of a session to restore context from a previous conversation'. Provides a clear when-to-use scenario. Does not explicitly state when not to use or mention alternatives, but the sibling list implies other session management tools for different purposes.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.