delimit_session_handoff

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

No annotations provided, so the description bears full burden. It discloses side effects (writes a handoff record via ai.ledger_manager.session_handoff) and behavioral details (coerces list inputs from comma strings). While it doesn't cover auth needs or rate limits, it provides significant context beyond the schema. A score of 4 is appropriate for missing some details like overwrite behavior.

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 extremely concise, using only a few sentences to convey purpose, usage, sibling contrast, and side effects. It is well-structured with clear headings (When to use, When NOT to use, Sibling contrast, Side effects) and front-loaded with the primary action. No wasted words.

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 the complexity (7 parameters, output schema exists, no annotations), the description covers purpose, usage guidelines, sibling distinction, and a behavioral quirk (coercion). It does not explain persistence details or if it overwrites previous handoffs, but the output schema likely fills gaps. Overall, it is quite complete for an AI agent to understand when and how to use the tool.

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 value by explaining that list parameters are coerced from comma strings via _coerce_list_arg, which helps the agent understand input flexibility. This goes beyond the schema's individual parameter descriptions.

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 tool clearly states it saves a session summary for cross-session continuity. It distinguishes itself from siblings (delimit_soul_capture and delimit_memory_store) by specifying it writes a structured handoff with explicit fields, while soul_capture writes a richer soul with git state and memory_store handles single-line memory.

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 provides when to use (at the end of a productive session) and when not to use (for richer cross-model state or single-line memory), with clear alternatives (delimit_soul_capture and delimit_memory_store). This is exemplary guidance for an AI agent.

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