Session Handoff

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

The description states 'Write' and 'auto-captures git state' (read-only), but annotations have destructiveHint=true, indicating potential destructive behavior. This is an annotation contradiction; the description provides no additional behavioral context beyond what annotations already contradict.

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 concise sentences with no wasted words. Front-loaded with the action and key features, making it easy to parse.

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?

While inputs are well-covered, the description lacks context about output or relationship with sibling tools like 'complete_handoff'. The auto-capture feature is clear, but the overall workflow is under-explained.

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%, baseline 3. The description adds meaning by explaining that git state is auto-captured (not needing parameters) and maps listed fields (lastTask, nextStep, blockers) to parameters, providing context 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 uses a specific verb 'Write' and identifies the resource as a 'session handoff primer' with clear auto-capture details (git state, tasks, blockers). It distinguishes itself from sibling tools like 'complete_handoff' and 'start_handoff' by focusing on creating the primer for continuity.

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 implies use at end of session for next-session context, but lacks explicit guidance on when not to use or how it differs from siblings like 'complete_handoff' or 'session_primer'. No exclusions or alternatives are mentioned.

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