telegram-transcribe-audio

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

Description adds async behavior details (returns immediately with transcriptionId and pending flag) and polling pattern. Annotations (readOnlyHint=false, openWorldHint=true) already indicate mutation and possible side effects; description does not contradict and adds useful context.

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?

Two sentences, front-loaded with main action and async behavior. Every sentence adds value; no fluff.

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 explains return fields (transcriptionId, pending) and how to get final result. Mentions Premium feature. Missing error handling or rate limits, but sufficient for typical use.

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 coverage is 100% with clear descriptions for both parameters. Description does not add extra semantics beyond the schema; it's adequate but not enhanced.

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?

Description clearly states it requests server-side transcription of voice/video notes, a Telegram Premium feature. It distinguishes from sibling telegram-get-transcription which is used for polling results.

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?

Explicitly tells when to use (initiate transcription) and when to use sibling (if pending:true, call telegram-get-transcription). Also notes the Premium requirement.

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