whatsapp_outbound_call

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say that a permission-request template must be sent first, that calls may fail if the user has not consented, or anything about the asynchronous nature of the result.

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?

A single short sentence with no wasted words and the action front-loaded, which is structurally fine for a title-style summary. But it is under-specified rather than concise in the helpful sense, and adds no sentence that earns its place beyond the tool name.

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 six-parameter, five-required mutation with no output schema and no parameter documentation, the description is far too thin. It omits the permission-request flow, the meaning of agent_id, and any distinction between this and the other outbound-call handlers, so an agent cannot confidently construct a 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?

Six parameters, five of them required, with 0% schema description coverage, and the description explains none of them. Critical fields like whatsapp_call_permission_request_template_name, its language code, agent_id, and the nested conversation_initiation_client_data are completely undocumented, leaving the agent to guess at formats and IDs.

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 verb and resource ('Make An Outbound Call Via Whatsapp'), which is enough to know it initiates a WhatsApp voice call rather than sending a message (cf. sibling whatsapp_outbound_message). However, it gives no detail about the permission-request/template mechanism that the required parameters imply, so it is barely more informative than the name itself.

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 guidance on when to choose this over sibling outbound-call tools such as handle_twilio_outbound_call, handle_exotel_outbound_call, or handle_sip_trunk_outbound_call, nor any prerequisites (e.g., WhatsApp account must exist, user must have granted call permission). Usage context is left entirely to inference.

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