session_handoff

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

With no annotations provided, the description transparently describes the tool's behavior: it stores progress, TODO lists, changed files, instructions, and incomplete work, and states that the next session automatically includes this handoff. It does not mention edge cases like overwriting, but provides sufficient behavioral context.

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 concise with no unnecessary words, front-loads the main action, and uses bullet points for clarity. Every sentence serves a purpose.

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 tool's complexity (7 parameters, nested objects), the description covers the main behavioral flow and the importance of calling it before closing. It could be more complete by explaining the instance_id parameter or the format of context_summary, but overall it adequately prepares the agent for correct usage.

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%, but the description adds value by explaining the purpose of each parameter in context (e.g., 'remaining_tasks: Tasks NOT yet done — the next window MUST pick these up' and for files_changed: 'marks partial/broken files so next window knows to fix them'). This goes beyond the schema's brief 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 description clearly states that the tool saves a detailed handoff for the next chat window, listing specific stored items and explicitly distinguishing itself from siblings like session_start and session_end by specifying when to call it (BEFORE closing a chat window).

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 explicitly instructs to call this tool BEFORE closing a chat window, especially if work is incomplete, and explains the consequence (prevents the 'continue' problem). It provides clear usage context but does not explicitly mention when not to use it.

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