download_chat_media

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

No annotations are present, so the description carries the full burden. 'Download media files in bulk' conveys the core action and implies files are saved locally, but it does not disclose behavior like writing to the filesystem, creating the output directory, overwrite behavior, or whether the operation is otherwise non-destructive to the chat. This is minimally adequate but lacks richer behavioral 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?

The description is one concise sentence with no filler. It leads with the action verb and includes the most important qualifying context, 'from a chat in bulk,' while leaving parameter details to the schema. Every part of the sentence earns its place.

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 description plus the fully documented schema is enough to understand the call surface, but with no annotations and no output schema, the description does not mention what the tool returns after download, where files are saved by default, or potential side effects/time costs. This is adequate but has clear gaps for an agent invoking a bulk-download tool.

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 100%, so the baseline is 3. The description adds little beyond the schema: 'photos, documents' echoes the media_type enum and 'bulk' loosely reflects the limit parameter. It does not clarify chat_id formats, output_dir semantics, or limit bounds beyond what the schema already states.

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 uses the specific verb 'Download' with a clear resource: 'media files (photos, documents) from a chat in bulk.' The 'in bulk' phrasing distinguishes it from the sibling tool 'download_media,' which likely handles individual media downloads. This is a precise, non-tautological statement of what the tool does.

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 implies usage when bulk media download from a chat is needed, but it does not explicitly state when to use this tool over alternatives such as 'download_media' or 'export_chat.' No exclusions, prerequisites, or alternative routing are provided. The 'in bulk' wording gives weak usage context but no direct guidance.

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