whatsapp_send_image

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

With no annotations, the description carries full burden. It only gives formatting hints for phone and image_url but omits side effects (e.g., message sending), auth requirements, error handling, or limitations (e.g., file size).

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 very concise (one sentence) and front-loaded with the core purpose. It could be slightly better structured, but every word adds value.

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 3 parameters, no annotations, and an output schema, the description is too minimal. It fails to mention return value, error cases, or any behavioral context beyond parameter hints.

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 description must add meaning. It explains phone format (no '+'), image_url type (public URL), and caption as optional. This is helpful but minimal; it lacks accepted image formats or size limits.

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 'Send image via WhatsApp', specifying the verb (send) and resource (image). It distinguishes from siblings like whatsapp_send_video or whatsapp_send_text by focusing on images. However, it lacks specificity on image format or size constraints.

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?

No guidance on when to use this tool vs alternatives like whatsapp_send_document. No prerequisites mentioned (e.g., WhatsApp connection status). The description provides no context for proper invocation.

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