ghl_conversation_download_message_transcription

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

Adds behavior the annotations cannot express: the response is not JSON but a text/plain attachment with a Content-Disposition filename, and it requires a Sub-Account (location) token. This is exactly the kind of transport/auth detail that prevents an agent from mis-parsing the result. No contradiction with readOnlyHint/idempotentHint.

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 most surprising fact (not JSON, file download) is front-loaded, which is the right ordering. There is mild redundancy — the title line 'Download transcription by Message ID' is repeated almost verbatim in the sentence below it — but the whole thing is packed with useful detail and easily parsed.

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?

With no output schema, the description takes on the burden of describing the return value and does so precisely (text/plain attachment, filename). Combined with the endpoint path, version header, and auth requirement, an agent has everything needed to call and handle this tool correctly.

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 100% with only locationId and messageId, both already documented. The description mentions 'passing the message id' but adds no format, source, or constraint information beyond the schema. Baseline 3 applies.

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?

States a specific verb (download), resource (message transcription), and scoping key (Message ID), and explicitly separates it from the near-identical sibling ghl_conversation_get_message_transcription by noting the '/download' path returns a file rather than JSON.

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 contrast with the non-/download endpoint tells an agent which of the two transcription tools to pick, but it stops short of a prescriptive rule ('use this when you need the raw text file; use the other for the JSON object'). Still, the alternative is named, which is well above average.

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