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

Adds substantial context beyond annotations: messages are delivered to real contacts (matching destructive/openWorld), a 50-reply batch cap, the 24h Meta messaging window, the send_wp_template fallback, and a per-reply result shape. This is exactly what an agent needs to avoid failing a bulk send.

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?

Three compact sentences, front-loaded with the action and the payload shape, then the delivery constraint and return value. No 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?

Covers payload shape, batch limit, delivery semantics, the WhatsApp template escape hatch, and the return granularity despite no output schema. Minor gaps remain on error/partial-failure behavior and auth/permission requirements for publishing to real contacts.

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 0% and the schema only declares an untyped array of objects, so the description carries the full burden and does it well: it documents the item keys (platform enum ig|fb|tw|wp, chat_id or chat_uuid, message) and the max-50 batch size.

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?

States a specific verb (send replies) applied to a specific resource (complaint conversations), and the [publish] tag signals the write scope. It is clearly distinguishable from chats_collect_complaints, though it does not explicitly rule out comments_send_complaint_replies or send_chat_message.

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 24h Meta window plus the note that WhatsApp messages outside it require send_wp_template gives an explicit conditional routing rule to a sibling tool. No explicit exclusion against the comments-based sibling, but the context is clear.

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