Download transcription by Message ID

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

Annotations already declare this as read-only, idempotent, and non-destructive. The description adds useful context such as the token requirement, scopes, and endpoint. However, it does not mention the response format or what happens when a transcription is unavailable, so it only partially supplements the annotations.

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 opens by repeating the title verbatim ('Download transcription by Message ID') and then immediately restates the same idea. The endpoint and scopes are useful, but the first phrase is redundant and adds noise rather than value.

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?

The tool is simple and annotations cover safety, but the description fails to differentiate this from conversations_get_message_transcription or explain what the downloaded payload looks like. With no output schema, that missing distinction and response clarity are important gaps.

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%, so both messageId and locationId are already explained as strings. The description restates the message ID concept but adds no real semantic detail beyond what the schema provides, so the baseline score of 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 states a specific verb and resource: 'Download the recording transcription for a message by passing the message id', and includes the exact endpoint. It is clear about what the tool does, but it does not distinguish itself from the similarly named sibling conversations_get_message_transcription.

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?

There is no guidance about when to use this tool versus conversations_get_message_transcription or conversations_get_message_recording. The description only explains the action and auth scopes, leaving the selection decision entirely to the agent.

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