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

With no annotations, the description carries the full burden of behavioral disclosure. It states the broadcast is a draft, never sends, lands ready for human review, and that consent and tier quotas are enforced in the composer. This meaningfully clarifies side effects and limits of the operation.

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 compact and front-loaded: it opens with the direct-call instruction and the draft-safety guarantee. The examples and audience/channel explanations each add necessary value, and no sentence is wasted.

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 tool with nested parameters and no output schema, the description covers purpose, usage, channel, audience, and send behavior well. The only notable gap is not explaining the default/omitted audience behavior or what the created draft returns, but overall it is sufficient for correct 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%, so the description must compensate. It adds useful semantics for channel (listing all six values), audience types (all, segment, tags), and match behavior (any/all). It leaves name and message to be inferred from context, but those are relatively self-evident.

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 identifies the verb and resource: 'Create a one-time broadcast as a DRAFT'. It also distinguishes the tool from generic content-creation siblings by specifying broadcast/announcement asks and explicitly noting it never sends. This is specific enough for an agent to tell it apart from similar create_* tools.

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 gives explicit when-to-use triggers with concrete user phrasings like 'broadcast the drop to my VIP tags on WhatsApp' and 'send a message to all my subscribers'. It also says to call directly without whoami or context lookup. It does not name an alternative tool, but the context is clear enough for most selection decisions.

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