download_conversation_transcript

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

With no annotations, the description carries the full load; it does add useful context by stating the required `messages:read` scope and showing that the operation is a GET (read-only) against a UUID-scoped path. It does not disclose the response format, size limits, or whether a transcript file is generated versus returned inline, which matters for a 'download' 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?

Very short and front-loaded: purpose, permission, endpoint, tags. The 'Tags: Conversations' line is auto-generated filler with no decision value, but the overall length is appropriate.

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?

There is no output schema, so the description is the only place to learn what a 'download' yields (file format, mime type, content shape) — and it is silent on this. Permission and endpoint coverage make it minimally viable for a single-parameter tool, but an agent cannot predict the result.

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 100%, but the schema's only annotation is '(path parameter)', so the description partially compensates by rendering the endpoint path with {uuid}, confirming the identifier is a path segment. It adds no meaning about where the UUID comes from or what it identifies.

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 name and opening line state a specific verb+resource ('Download Conversation Transcript'), which is clearly distinct from siblings like get_conversation or get_conversation_participants. However, the description adds no explicit contrast to those siblings, so differentiation is inferred from the name alone.

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 only usage-relevant content is the prerequisite 'Requires the `messages:read` permission'. There is no guidance on when to download a transcript versus fetching the conversation, nor any mention of when this tool is inappropriate.

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