jambavan_session_handoff

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

With no annotations provided, the description discloses key behaviors: idempotency, inclusion of memories/rin/git status, and share_safe redaction. It is transparent about the dual-mode operation, though could detail return value format.

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?

Two sentences, each earning its place: first defines core functionality, second explains the bidirectional nature with idempotency. No fluff, well front-loaded.

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 no output schema, the description is fairly complete, covering inputs and behavior. However, it does not describe the return value for import (e.g., success status) or export format details, which would be helpful.

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%, so baseline 3. The description adds value by explaining the dual mode (omit text to export, pass text to import), which is not obvious from parameter descriptions alone. It also clarifies share_safe and other flags.

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 specifies the tool moves session context as a markdown document, with clear verb 'move' and resource 'session context'. It distinguishes itself from siblings like jambavan_memory_store by focusing on session handoff with export/import modes.

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 explains export vs import modes and idempotency, providing clear usage context. However, it does not explicitly mention when not to use or compare to alternatives like jambavan_memory_store, which would be helpful given many siblings.

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