whatsapp_save_media

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

No annotations are provided, so the description carries the full burden. It does not say where the media is written, whether it overwrites existing files, whether a connected WhatsApp account is required, or what happens if the message has no media or the media has expired. The only disclosure is the enumeration of supported media types.

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 single sentence is front-loaded with the verb and resource and wastes no words, but it is visibly truncated ("...or a voic"), indicating incomplete content rather than genuine conciseness.

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 write/side-effecting tool with no annotations, no output schema, and no parameters, the description should explain the destination path or return value and the target-message mechanism. It does none of these and is cut off, leaving the agent unable to predict the outcome of the call.

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 declares zero parameters and coverage is 100%, so per the baseline rule this is a 4. However, the description gives no hint as to how the target message is identified (presumably from conversation context), which is a real ambiguity given the empty schema.

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?

States a specific verb ("Saves") and a specific resource ("the media of one WhatsApp message"), then enumerates the media kinds (PDF/DOCX/XLSX, image, video, voice). This distinguishes it from whatsapp_read_messages, but it never differentiates from close siblings like save_attachment or whatsapp_send_file, and the sentence is truncated mid-word.

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 statement of when to use this tool versus alternatives (save_attachment, whatsapp_send_file, media_probe) and no preconditions such as needing to have read the message first. The agent must infer usage entirely from the name.

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