conversations_download_message_transcription

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

The annotations already convey readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds minimal behavioral context—it does not state what format the downloaded transcription takes (e.g., file, text) or any side effects. Since annotations cover the safety aspects, a score of 3 is appropriate.

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 a single, compact sentence with no wasted words. It is front-loaded with the primary action and identifier, making it easy to scan. Slightly more detail on output would be useful, but the brevity is a strength.

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 does not clarify what the 'download' actually returns—whether it is a file, text, or a URL. It also lacks context about the relationship to message recordings or transcriptions. For a simple read operation, the description could be considered minimal but leaves an agent uncertain about the response format, which is a functional gap.

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 schema description coverage is 100%, so both parameters (messageId and locationId) already have descriptions in the input schema. The description mentions messageId but not locationId, adding only marginal emphasis. As the schema fully documents parameters, the description does not need to add much; baseline 3 is justified.

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 'Download transcription by Message ID' clearly states the action (download) and resource (transcription) with the key identifier (Message ID). It is specific enough to understand the core function, but does not differentiate from the sibling conversations_get_message_transcription, which may overlap in intent. The name 'download' vs 'get' hints at a file retrieval but is not explicitly clarified.

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?

No guidance is provided on when to use this tool versus the sibling conversations_get_message_transcription or conversations_get_message_recording. There is no mention of prerequisites, scenarios, or exclusions. An agent is left to infer which tool to choose based solely on the name and description.

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