download_media

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

With no annotations, the description does at least disclose the key side effect—writing a file to local storage—and the shape of the result (a local path). It says nothing about what happens when the message has no media, permission requirements, file size limits, or whether files are overwritten, which are meaningful gaps for a no-annotation tool.

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?

A single compact sentence with the action front-loaded and the return value trailing; nothing is wasted. It is arguably too terse rather than bloated, but structurally it is clean.

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 is simple (two required params) and an output schema exists, so return-value detail is not owed. However, given zero parameter documentation and no annotations, the description leaves the agent without enough context on identifier formats and failure conditions.

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 both parameters are bare ('chat': string, 'message_id': integer) with no titles beyond their names. The description only vaguely implies the parameters ('from a message') and adds nothing about chat identifier format (ID vs. username) or message_id scoping, leaving the required schema burden unmet.

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 pairs a specific verb (Download) with a specific resource set (photo/video/voice/file) and scopes it to 'from a message', so an agent knows exactly what operation this is. It also names the return value ('returns local path'), but it does not explicitly distinguish itself from siblings like send_file, which is the main remaining ambiguity.

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?

There is no when-to-use guidance, no preconditions (e.g. the message must actually contain media, or how to obtain a message_id first), and no mention of alternatives or follow-up tools. The agent must infer the entire workflow context.

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