get_session_handoff

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses only that the returned handle is 'durable' and enables cross-connection resumption. It says nothing about whether calling it mutates or creates server-side state, whether the handle is sensitive/credential-like, whether it expires or is single-use, or what happens if the passed session_id is unknown.

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?

A single sentence with the purpose front-loaded and no filler; nothing is redundant. It is appropriately sized for what it says, though the terseness is a symptom of missing content rather than efficient compression.

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 no annotations, no output schema, and two undocumented optional parameters, the description is the only explanatory channel and it under-delivers: it does not state what the returned handle looks like or how to use it, nor how the defaults on 'goal' and 'session_id' behave. For a tool whose whole point is producing a token for later reuse, that usage contract should be spelled out.

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 0% for two parameters, and the description provides no compensating meaning for either. It never explains what 'goal' influences (both params are optional with defaults) or how 'session_id' selects a prior session versus establishing a new one, leaving an agent to guess the semantics of both fields.

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 + resource ('Return the durable session handle') and adds the purpose clause 'needed to resume private memory in a new connection', which tells an agent what the artifact is for. It does not, however, distinguish this from siblings such as session_status or list_recent_sessions, and 'handle' remains an ambiguous noun (token? ID? opaque blob?).

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 phrase 'to resume private memory in a new connection' implies the triggering situation, so usage is inferable rather than absent. There is no explicit when-not guidance, no mention of what to do if a session already exists in this connection, and no named alternative among the ten sibling memory tools.

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