export_conversation

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

Description lacks detail on what happens to the exported file (e.g., local save vs. return as text), permission requirements, or side effects. With no annotations, this is a significant gap for a write-like operation that produces output.

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?

Single sentence with no unnecessary words, but lacks structural separation of purpose and usage. Could be improved by adding a second sentence for guidelines.

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?

Adequate for a simple export tool with well-documented parameters and no output schema. However, missing details like export destination (local path? returned via tool?), which would help completeness.

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 covers all three parameters with clear descriptions, so baseline is 3. The description adds no extra meaning beyond the schema (e.g., it mentions markdown or JSON, but the enum already lists those).

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?

Description clearly states the verb 'export' and resource 'Claude Code conversation', with explicit output formats (markdown or JSON) for backup or sharing. This fully differentiates from sibling tools like archive_conversations or search_conversations.

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?

No guidance on when to use this tool versus alternatives like archive_conversations or list_backups. The description assumes the agent knows the context, which reduces utility for correct tool selection.

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