session_handoff

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

No annotations provided, so description carries full burden. It explains state persistence, cross-agent accessibility, and importance of thorough summaries. Does not mention error conditions or overwrites, but sufficient for a state-saving tool.

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?

Front-loaded with critical instruction ('CALL THIS LAST'). Each sentence is purposeful, though some redundancy in parameter descriptions could be trimmed. Generally concise.

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?

With output schema present, return values are covered. Description covers purpose, usage, parameters thoroughly. Could mention consequences of not calling, but overall complete for a handoff 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%, but description adds meaningful guidance: 'Be specific — this is your only record' for summary, and ordering hint for next_steps. Adds value beyond 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?

Description clearly states the tool saves session state for the next session, with a specific verb ('CALL THIS LAST') and resource distinction. Sibling session_context is mentioned as the retrieval counterpart, so it's well-differentiated.

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 says to call it last before session ends and references session_context for retrieval. Does not list when not to use, but context makes it clear it's for end-of-session handoff.

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