download_media

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

The description usefully discloses the default download directory and that the tool returns a path, which goes beyond the bare schema. However, with no annotations available, it omits important behavioral details such as error handling for missing attachments, overwrite behavior, and whether directories are created.

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 compact and front-loaded with the core action. Every sentence contributes meaningful information: what it does, what it returns, and where files go by default.

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 basics are present: required parameters are indicated by the schema, and the return value is noted. Still, the lack of annotations and absence of failure-mode or precondition information leaves the description only minimally viable for correct invocation in edge cases.

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 0%, so the description must compensate, but it only clarifies the out_dir default via TELEGRAM_MCP_DOWNLOAD_DIR. The semantics of chat and message_id are left entirely to their schema titles, with no format, resolution, or usage context provided.

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 operation: download a message attachment to a local file and return the path. This distinguishes it from siblings like send_file (uploading) and get_message (retrieving message data).

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 given about when to use this tool versus alternatives such as get_message or send_file. Prerequisites like the message actually containing an attachment are not mentioned.

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