Save a claude.ai conversation to a file

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

With no annotations provided, the description carries the full burden. It clearly states the write-to-disk action and markdown format, but does not disclose whether existing files are overwritten, whether directories are created, or any error handling. This leaves some behavioral ambiguity for a file-writing tool.

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 a single sentence, front-loaded with the action verb and resource, then a practical use case. There is no filler or repetition.

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's moderate complexity (file write with a timestamp option) and lack of annotations/output schema, the description covers the primary purpose and use case but omits edge behaviors like overwriting, file path handling, and return value. This is adequate but not fully complete.

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 coverage is 67% (path and uuid are described, include_timestamps is not). The tool description adds no parameter context; it does not explain what include_timestamps does or how the parameters interact. The description does not compensate for the partially missing schema documentation.

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 action: 'Fetch a claude.ai conversation and write it to disk as markdown.' It specifies the resource (claude.ai conversation) and output (markdown file), and distinguishes itself from siblings by emphasizing persistence to disk rather than just reading or listing.

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 gives a clear use case: 'useful for parking it in the repo (e.g. docs/context/) so it persists across sessions.' This implies when to use it, though it does not explicitly name alternatives or state when not to use it.

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