jambavan_session_export

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

With no annotations provided, the description carries the full burden. It discloses that the tool produces a self-contained markdown document and lists included data types. It does not mention side effects, authentication needs, or rate limits, which are not critical for this export tool. The description adds useful context but lacks comprehensive behavioral details.

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 extremely concise—two sentences that front-load the core purpose and immediately follow with usage and output details. Every sentence earns its place with no wasted words.

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 5 parameters (none required), no output schema, and no annotations, the description adequately explains the tool's purpose, contents, and use case. It could mention the output format more explicitly, but it does describe it as 'self-contained markdown' and explains how to use it to resume context.

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 100%, so the baseline is 3. The description does not elaborate on individual parameters beyond what the schema provides. It adds value by describing the overall output contents but not parameter specifics.

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 exports current session context as a portable handoff document, lists specific contents (memories, rin debt markers, git status), and distinguishes its use case from siblings like jambavan_session_import by specifying it is for transfer to new sessions, hosts, or colleagues.

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 explicitly states when to use the tool (to transfer context to a new session, different host, or colleague) and describes the output format. However, it does not provide exclusions or mention alternative tools, though the context implies the import sibling.

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