import_claude_export

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

No annotations provided, so description carries full burden. It explains input (file path), prerequisite (download/untar), and output (structured list). Does not mention any side effects or permissions, but as a read operation, this is adequate.

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?

Description is relatively long but well-structured, front-loading the core action and then providing usage steps. Every sentence adds value, though some could be consolidated. Still, it's efficient for the complexity.

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 no output schema, the description explains the return value type. It also provides a complete workflow for the AI after tool use, covering analysis and follow-up tool calls. Highly complete for the intended use case.

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?

Only one parameter 'filePath' with schema coverage 100%. Description adds workflow context about how to obtain the file, which helps the AI guide the user. Baseline 3 is elevated because the description enriches understanding beyond the schema.

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 'Read a conversations.json file... and return a structured list of conversations.' Specifies the exact file and output format, distinguishing it from sibling tools like add_idea or export_html.

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?

Explicitly instructs on prerequisites (user must download data from Claude.ai), step-by-step usage, and post-call actions for the AI, including how to organize results. Leaves no ambiguity about when and how to use.

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