Export a conversation

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

Annotations include readOnlyHint=true, so the safe, non-destructive nature is already known. The description adds behavioral context by enumerating the output formats and asserting that 'Every format re-imports', which is a key property beyond the annotation. It does not mention response details (e.g., whether the output is a string or file), but given the read-only hint and simple nature, this is adequate. No contradictions with annotations.

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 two sentences with no filler. The first sentence front-loads the core action and enumerates formats; the second adds the re-importability trait without redundancy. Every clause earns its place, and the structure is tight and efficient.

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?

For a tool with only two parameters and no output schema, the description covers the essential usage context: what formats are available and that the export is round-trippable. It could explicitly state that the tool returns the exported content as a string, but given the tool's name and purpose, that is largely inferred. The description is complete enough for an agent to select and invoke the tool 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%, so the description must illuminate parameters. It adds meaning to the 'format' parameter by expanding each enum value (e.g., 'Markdown transcript', 'chat-completions message array'), which goes beyond the raw enum names. However, it does not provide additional context for 'conversationId' beyond what the schema already implies (a UUID identifier). The description partially compensates for the coverage gap but could clarify the purpose of the id more explicitly.

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's function: 'Writes a stored conversation back out in another client's format' and lists all supported formats (Markdown, brief, chat-completions, etc.). This distinguishes it from siblings like import_conversation (opposite direction) and get_conversation (likely native format). The verb 'writes...back out' plus the resource 'conversation' and the explicit scope of format conversion make the purpose unambiguous.

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 implies usage for cross-client exports via 'another client's format' and notes that 'Every format re-imports', suggesting interoperability. However, it does not explicitly state when to use this tool over alternatives (e.g., use get_conversation for native retrieval, import_conversation for incoming). No 'when-not-to-use' guidance or comparison to siblings is provided, so the agent must infer the appropriate context.

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