prepare_handoff

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

Annotations already set readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral context by clarifying the tool only imports reference context and does not grant execution rights for the original instructions. This goes beyond the annotations without contradicting them.

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 two short sentences with no filler. The main action is front-loaded, and the safety caveat about original instructions earns its place. This is concise and well-structured.

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?

The description covers core purpose and a key limitation, but with 5 parameters, no output schema, and sibling tools, it leaves gaps around parameter semantics and when to choose this tool versus read_session/list_sessions. It is minimally adequate but not fully complete.

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 only 40%, and the description does not compensate by explaining parameters like sessionId, maxChars, or maxMessages. It implicitly references the selected session and current tool, but it leaves important parameter semantics unexplained.

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 verb and resource: it imports a selected session into the current tool as reference context for continuation. It also distinguishes itself from executing original instructions, but it does not explicitly differentiate itself from the sibling tools read_session or list_sessions.

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 provides clear usage context: use this when you need to bring a prior session into the current tool as reference context. It also warns that original instructions are not execution authorization, which is a useful when-not. However, it does not explicitly mention alternatives or when to prefer read_session/list_sessions.

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