Load a past Claude Code conversation

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

With no annotations, the description details the output content (elided tool outputs, collapsed summaries) and parameters (turns range, maxTokens limit, includeThinking). It is transparent about what the tool does and does not include, though it could mention error handling or side effects.

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 well-structured, front-loading the main action and then providing parameter guidance. It is concise with no redundant sentences, though slightly longer than 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?

Given 6 parameters, no output schema, and multiple siblings, the description covers key aspects: parameter usage, alternative tools for large sessions, and output format. It is complete enough for an agent to use correctly, though it lacks return value details beyond the initial statement.

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?

100% schema coverage, and the description adds significant value: explains id source (list_sessions/search_sessions), turns syntax (e.g., '300-340'), default format (compact), default maxTokens (16000), and the meaning of includeThinking. This goes well beyond the schema.

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 it loads a past conversation as compact Markdown, specifying what is included (human turns, collapsed tool-call summaries, assistant replies) and what is elided (tool outputs). It distinctly differentiates from siblings like list_sessions and session_outline.

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 says when to use: 'Use this to pull a previous conversation's context into the current session.' Provides when-not-to-use guidance for large sessions, suggesting session_outline or search_in_session instead, and references alternatives like list_sessions/search_sessions for ids.

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