Delimit Session History

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

Annotations already declare readOnly/idempotent/non-destructive, and the description reinforces this with 'Side effects: read-only' while adding the implementation target (ai.ledger_manager.session_history) and what the recovered content consists of. It stops short of describing edge cases or empty-state behavior, so not a 5.

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 front-loaded with a one-sentence summary followed by clearly labeled sections for usage, exclusions, sibling contrast, and side effects. Every line earns its place; there is no filler or repetition of the title.

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 simple read-only tool with one optional parameter, an output schema, and annotations covering safety, the description covers selection context, usage timing, sibling distinctions, and side effects. Nothing needed for correct invocation is missing.

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 the only parameter, limit, is already documented in the schema with its default. The description's 'last N runs' is largely a restatement of 'recent sessions' and adds no new constraints such as minimum/maximum values or ordering rules.

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 opens with a specific action and resource: 'Load recent session handoffs for context recovery.' It then contrasts itself with siblings (delimit_session_handoff writes, delimit_revive reads soul state), making its role unmistakable.

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?

It provides an explicit 'When to use' section (session start, to recover completed items, decisions, blockers) and an explicit 'When NOT to use' section naming the correct alternatives. This removes ambiguity for an agent selecting between read and write handoff tools.

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