transfer_session

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

With no annotations, the description carries the full behavioral burden and does so thoroughly: it states what the returned artifact contains, what it cannot do (restore provider-private runtime state), and that historical tool calls are read-only and must not be executed automatically. This is a strong safety and limitation disclosure.

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 three sentences, front-loaded with the core purpose, followed by usage constraint, then content/limitations/safety. No filler or repetition.

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 tool is low-complexity (one parameter, output schema present), and the description supplies all needed behavioral context: when to use it, what it returns, what it cannot preserve, and a safety warning. Nothing essential is missing for an agent to invoke it correctly.

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%, and the description adds no guidance on session_id despite being the only and required parameter. It never explains where to obtain the session_id or how it is validated, so the description does not compensate for the schema's minimal 'Session Id' text.

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 opens with a specific verb ('Download') plus a precise resource ('the full captured session') and outcome ('secure local artifact for another AI tool'). It also contrasts with 'a summary', which distances it from summarize_session and other retrieval siblings.

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?

It gives an explicit invocation condition ('Use only when the user explicitly asks to move or load the whole session rather than a summary'). However, it does not name sibling tools like get_session or summarize_session as alternatives, so agents must infer the routing boundary from context.

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