whatsapp_upload_media

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

With no annotations provided, the description carries full burden, but it only states the high-level action. It fails to disclose critical behavioral traits such as that the media is fetched from a URL (media_url), authentication requirements (bearer_token), or potential limitations (file size, supported types, error behavior).

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 a single sentence, which is concise, but it is too terse given the tool's complexity. It could benefit from a second sentence clarifying the URL-fetching behavior or parameter roles without being overly verbose.

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?

Given the tool's 5 parameters, no output schema, and no annotations, the description is incomplete. It does not explain how the media ID is returned, the prerequisites for using the bearer token, or the typical workflow (upload first, then use ID in send_media). This leaves significant gaps for an agent.

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 only 40% parameter description coverage, yet the description adds no context for the parameters (e.g., bearer_token, phone_number_id, filename). It does not explain the purpose of each parameter beyond what the schema already provides, leaving the agent with insufficient information.

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 states the action (upload media file), the target system (WhatsApp), and the result (get a media ID for use in messages). It is specific and distinct from sibling tools like whatsapp_send_media which sends media to a user.

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 provides no guidance on when to use this tool versus alternatives like whatsapp_send_media or whatsapp_send_text. It lacks any context about prerequisites, workflow, or when-not-to-use, which is essential given the multiple WhatsApp-related sibling tools.

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