import_session

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 deferred nodes become active, resolved and adopted decisions carry forward, and it returns a summary. It does not describe potential merge conflicts or side effects, but the merge semantics are reasonably clear.

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?

Three short sentences, each earning its place. The first sentence states the purpose, the second gives input details, and the third describes the output. No fluff.

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 the tool has one parameter and an output schema (though not shown), the description covers the input format, the merging behavior, and the return value. It is complete for a simple import operation.

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?

The input schema has one parameter 'json_str' with no description (0% coverage). The description adds essential meaning by stating it expects the 'JSON content of a .chatgraph.json file', which compensates for the schema gap.

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 starts with a clear verb+resource: 'Load a prior session graph and merge it into the current session.' It explicitly states what the tool does and distinguishes it from sibling tools like export_session.

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 specifies the source of the input ('JSON content of a .chatgraph.json file from export_session or fish-bridge export'), providing clear context. However, it does not explicitly state when not to use it or mention alternatives, though export_session is implied as the counterpart.

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