conversation_import

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

With no annotations provided, the description carries the behavioral transparency burden. It does add a valuable behavioral trait by specifying idempotency keyed on (source, external_id), but it does not disclose what happens on conflict, whether this creates/updates records, or any side effects beyond the import.

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 very short, front-loaded with the core purpose, and then adds the key behavioral detail of idempotency. There is no unnecessary padding, though the opaque '(§3.15, D25)' reference is mildly cryptic.

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 nine parameters, no annotations, and no in-schema parameter descriptions, the description is too thin to be fully actionable. It omits important context such as expected content format, source value domain, how optional fields are used, and the effect of duplicate external_id imports.

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 only clarifies source and external_id as the idempotency tuple. The required title and content parameters, plus all optional parameters, receive no semantic explanation beyond their names.

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 states a specific action and resource: importing a raw transcript from an AI console. This clearly distinguishes the tool from sibling read/search tools like conversation_search and conversation_get.

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?

There is no explicit guidance on when to use this tool versus alternatives, and no exclusions or prerequisites. The import action is implied, but the description does not help an agent decide between this and other write/import tools in the sibling list.

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