Read a claude.ai conversation

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

No annotations provided, so description carries full burden. It states 'fetch' (a read verb) and 'as markdown' which discloses return format. However, it does not explicitly disclose that this is read-only, nor does it mention truncation behavior or any potential side effects, though the schema covers max_chars. It's adequate but not rich.

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?

One sentence, 20 words, front-loaded with verb and resource. No fluff.

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 simple read tool with three params and no output schema, the description plus schema cover the core need: what it does, output format, and use case. However, it doesn't mention error conditions, authentication, or relationship to debug_connection, but these are not critical for successful invocation.

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 67% (uuid and max_chars described). Description adds no parameter-specific info, but the schema's uuid description links to list_web_conversations, and max_chars explains truncation. The include_timestamps parameter lacks description in both schema and tool description, leaving a gap.

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 uses specific verb 'fetch' and resource 'full transcript of one claude.ai conversation', with output format 'markdown'. It clearly distinguishes from siblings like list_web_conversations (which lists conversations) and save_web_conversation (which likely saves/shares).

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?

Provides clear context: 'so it can be used as context in this Claude Code session' indicates when to use. However, it does not explicitly mention alternatives or when not to use, though the sibling list tool is implied through the schema's uuid reference.

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