conversations_get_message_transcription

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds no additional behavioral context—it doesn't describe return format, error behavior, or any side effects. With the bar lowered by annotations, a 2 is appropriate because the description still fails to add meaningful behavioral information.

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, short sentence that is front-loaded with the core action, making it concise and easy to parse. While it is sparse, that's a matter of completeness rather than structure, so it earns a 4 for conciseness.

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 has no output schema, so the description should at least indicate what the transcription retrieval returns (e.g., text, URL, or an error). It doesn't, leaving the agent with no information about the expected response. For a simple tool, this is a significant gap that prevents the description from being 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 schema description coverage is 100%, and the input schema already documents both messageId and locationId with clear descriptions, including the default behavior for locationId. The description does not add any parameter-specific semantics, so the baseline score of 3 is correct.

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 verb 'Get' and the resource 'transcription' keyed by Message ID, making the primary action unambiguous. However, it does not differentiate this tool from closely related siblings like conversations_get_message_recording or conversations_download_message_transcription, so it falls short of a 5.

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 provides no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. An agent must rely solely on the tool name and context to infer appropriate usage, which is insufficient.

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