fetch_media

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

With no annotations, the description carries the transparency burden and does well: it discloses the download side effect, the return value (local file path and transcript), and cache/redo behavior via force=True. It omits minor operational details like auth and rate limits, but the core behavior is clearly disclosed.

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?

Three sentences, front-loaded with the core purpose Diamonds: download media and derive text. Each sentence adds distinct information; no filler or repetition.

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?

Covers purpose, actions, return value, caching behavior, and a cross-tool note about get_messages. Missing explicit guidance on the wait parameter and edge-case behavior, but for typical invocation it is largely sufficient.

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 0%, so the description must compensate. It clearly explains the action parameter values and force behavior, but the wait parameter is never described serving, and chat_id/msg_id are only implied by the examples. Partial compensation only.

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 states a specific verb and resource: “Download a message’s media to local disk and derive text from it.” It also enumerates the action variants (auto, download, transcribe, extract), which makes the tool’s purpose unambiguous and distinct from generic sibling tools.

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 gives clear usage context by noting that voice messages are already transcribed upon arrival and advising the agent to check get_messages first. It does not explicitly list exclusions or alternative tools for other cases, but the guidance is practical and actionable.

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