session_handoff

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

Annotations are neutral (no destructive hints, etc.). Description adds value by explaining that state is saved and persisted across sessions, and that session_context will retrieve it. It clarifies the persistence behavior beyond the schema, though it doesn't detail error handling or idempotency.

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 well-structured with an initial imperative, explanatory paragraph, and bulleted Args section. It is somewhat verbose but every sentence contributes purpose. Could be tightened slightly.

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 existence of an output schema (not shown but signaled), return values need not be explained. The description covers purpose, usage, parameter semantics, and behavioral context (state persistence). It is complete for an agent to understand the tool's role in session management.

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?

Despite 0% schema description coverage, the description provides thorough guidance for each parameter: summary should be thorough, next_steps in priority order, in_progress as task IDs. This adds significant meaning beyond type definitions.

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 the tool saves session state (what you did, in-progress, next steps) at end of session. It distinguishes itself from sibling session_context, which retrieves this saved state. The verb 'CALL THIS LAST' provides a specific action and context.

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 this tool last before session ends, and links to session_context for retrieval. It provides clear when-to-use and implies when-not-to-use. The description even mentions alternative tool for loading state.

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