Send a freeform WhatsApp message. Requires an open 24h session (use get_whatsapp_session_status to check).
| Name | Required | Description | Default |
|---|---|---|---|
| message | Yes | Max 4096 chars | |
| sender_id | Yes | ||
| recipient_phone | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | ||
| message | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already convey mutation and non-idempotence. Description adds session requirement as a behavioral constraint. No further details on side effects or failure modes.
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?
Two sentences: first states purpose, second adds prerequisite. No waste, front-loaded.
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?
Adequate for a simple send action but lacks parameter details and does not explain output schema or error conditions. With sibling tools, more distinction could help.
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 only 33% with only 'message' described. Description adds no meaning for 'sender_id' or 'recipient_phone', leaving them undocumented.
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?
Clear verb 'Send' and resource 'freeform WhatsApp message'. Distinguishes from send_whatsapp_template by specifying freeform. Also mentions prerequisite session, adding clarity.
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?
Explicitly states prerequisite (open 24h session) and suggests using get_whatsapp_session_status to check. However, does not compare with sibling tools like send_sms or send_message.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target distinct resources and actions clearly (e.g., create_assistant vs create_campaign). However, there is some overlap like get_outbound_assistants vs get_assistants and list_all_phone_numbers vs get_phone_numbers, causing minor ambiguity.
Tools follow a consistent verb_noun pattern with underscores (e.g., create_document, delete_label, get_voices). Only minor deviations exist, such as generate_ai_reply and list_all_phone_numbers, but overall the pattern is maintained.
With 75 tools, the server is excessively large. Although the domain is broad (assistants, calls, messaging, etc.), the number of tools makes it difficult for agents to navigate and select the correct one, reducing coherence.
The tool set covers CRUD operations for most resources, plus webhooks, AI replies, and reference data fetching. Minor gaps exist (e.g., no delete_conversation, no attach phone number to assistant), but the surface is largely comprehensive for the platform's purpose.
