send_conversation_message

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

With no annotations, the description carries the transparency burden. It discloses useful traits like freeform vs. templated sending and the client_temp_id dedup key, but it does not mention side effects (e.g., message persistence/delivery), required permissions, or rate limits. It stops short of being fully transparent for a mutating action.

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 front-loaded with the core purpose, followed by a compact Args block. Every sentence contributes meaningful guidance, with no redundancy or filler.

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?

The tool is well-covered given its moderate complexity: all parameters are explained, an output schema exists, and usage boundaries are explicit. It lacks minor operational details such as failure modes or auth prerequisites, but these are not critical for selection and invocation.

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 description coverage is 0%, but the Args section fully compensates by explaining all four parameters: conversation_id target thread, body message text required, media_urls optional media list, and client_temp_id optional dedup key. This adds meaning far beyond the raw 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?

The description opens with a specific verb+resource: 'Send an outbound message into an existing conversation.' It also distinguishes this tool from templated WhatsApp sends, clarifying its exact scope.

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?

Provides explicit when-to-use guidance: 'For SMS / WhatsApp freeform replies' and direct alternative guidance: 'Templated WhatsApp sends should use the agent's WhatsApp template config instead of this tool.'

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