tg_download_many

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

With no annotations, the description must disclose behaviors itself. It states the 50-item limit and the default download directory, which is helpful. However, it omits details like file overwriting, permissions, error handling, or side effects on the filesystem, leaving some operational uncertainty.

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 highly concise: a two-sentence summary plus a compact Args block. Every sentence contributes meaning, with no redundancy or filler.

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?

For a simple batch download tool, the description covers purpose, parameters, a key constraint (max 50), and the source of IDs. It omits edge-case behaviors, but the presence of an output schema likely covers return values, so this is acceptable.

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 has zero descriptions, so the description compensates fully. The Args section clearly explains each parameter: chat, message_ids, and dest, including the default path for dest. This adds meaning beyond the schema's bare type definitions.

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 identifies the tool's function: downloading multiple attachments at once, with a specific maximum of 50. It also directs users to retrieve IDs from tg_media, which distinguishes it from the sibling tool tg_download for single-file downloads.

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?

It provides practical context: batch downloads with a max of 50, and instructs users to obtain message IDs from tg_media. While it doesn't explicitly mention preferring tg_download for single files, the phrasing 'several at once' implies the appropriate use case.

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