ghl_conversation_download_message_transcription

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

Annotations already provide readOnlyHint, idempotentHint, etc. The description adds that the response is a file download (text/plain) with Content-Disposition header, which is beyond the annotations. No contradictions.

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 somewhat verbose with repetitive phrases ('Download transcription by Message ID' and 'Download the recording transcription...'), and includes technical endpoint details that may not be needed. It could be more concise.

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 adequately explains the response format (text/plain file download), provides the endpoint and required scopes. It does not explain prerequisites like needing an existing transcription, but for a simple download tool it is fairly 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?

The input schema has 100% description coverage for both parameters. The description does not add new meaning beyond what the schema provides (just 'messageId' and 'locationId'). Baseline 3 is appropriate.

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 tool downloads a transcription file (text/plain) for a given message ID, and explicitly distinguishes it from the sibling tool that returns JSON. The verb 'download' and resource 'transcription by message ID' are specific and actionable.

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 explains when to use this tool (to download a transcription as a file) versus the alternative GET /transcription endpoint, and lists required OAuth scopes. While it does not explicitly state when not to use it, the distinction is clear enough.

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