session_load

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

With no annotations, the description carries the behavioral burden. It discloses that this is a load/retrieval action, returns a handoff brief of roughly 250 tokens, and is intended as the session-start context retrieval mechanism. It does not explicitly state 'read-only' or discuss side effects, but 'load' strongly implies non-mutating behavior and the return-size hint adds useful precision.

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 two tight sentences with no filler. Key information is front-loaded: the action, the timing, and the expected return size. Every sentence earns its place.

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?

For a tool with three parameters, full schema coverage, and no output schema, the description covers the essential operational context: when to call, what it loads, and what the returned content looks like. It could be more explicit about load_level variations, but the schema already handles those.

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 100%, so all three parameters are already documented. The description adds no new parameter-level detail beyond aligning with the default 'handoff' load level via the phrase 'handoff brief,' which is only marginal added value.

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 states a specific verb and resource: 'Load the handoff from a previous session.' It clearly identifies the tool's core purpose and differentiates it from siblings like session_status or session_search through the 'handoff' and 'new session' framing, though it does not explicitly name an alternative.

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 description gives clear timing guidance: 'Call at the START of a new session to get context from the last one.' This tells an agent when to use the tool, but it does not explicitly state when not to use it or compare it with sibling loading/checkpoint tools.

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