broadcast_message

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

With no annotations, the description carries the full burden. It discloses that delay is enforced automatically with a 30s minimum, which is a behavioral trait. However, it does not mention error handling, idempotency, or whether messages are queued or sent synchronously.

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 two sentences with no unnecessary words. It front-loads the core purpose and then adds constraints, achieving high density of useful information.

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 7 parameters and no output schema, the description is too brief. It fails to explain the relationship between delay, delay_min, delay_max (fixed vs random range), and does not describe label or media_url parameters. The return value or error behavior is also not mentioned.

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 100%, baseline 3. The description adds value by specifying the maximum numbers constraint (not in schema) and clarifying that delay is enforced with a minimum of 30s, which complements the delay parameter's description.

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 it sends a WhatsApp message to multiple recipients, distinguishing it from sibling send_message which likely targets a single recipient. It also specifies the limit of 1000 numbers per call.

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 key usage constraints: max 1000 numbers and minimum 30s delay between sends. It implicitly guides the agent to use this tool for bulk messaging versus send_message for single messages, but lacks explicit when-not-to-use or alternative guidance.

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