whatsapp

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions operations like 'send messages, manage campaigns and templates' but does not disclose critical traits such as authentication requirements, rate limits, whether operations are read-only or destructive, or what happens on success/failure. For a multi-operation tool with no annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence: 'WhatsApp messaging - send messages, manage campaigns and templates'. It is front-loaded with the main purpose and lists key functions without unnecessary detail. However, it could be slightly more structured by explicitly separating operations or adding brief context, but it earns high marks for brevity.

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 the tool's complexity (9 parameters, multiple operations including mutations like create/delete, no output schema, and no annotations), the description is incomplete. It fails to address behavioral aspects, output expectations, error handling, or how operations interact. For a tool with such scope and no structured support, the description should provide more context to be adequately helpful.

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 100%, so the input schema already documents all parameters thoroughly. The description adds no additional meaning beyond the schema—it does not explain parameter relationships, usage examples, or constraints. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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 the tool is for 'WhatsApp messaging - send messages, manage campaigns and templates', which gives a general purpose but lacks specificity. It mentions multiple operations (send, manage) without distinguishing which specific operations are available or how they differ from sibling tools like 'sms' or 'campaigns'. The purpose is clear at a high level but vague about scope and differentiation.

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 no guidance on when to use this tool versus alternatives. It does not mention when to choose WhatsApp messaging over sibling tools like 'sms' or 'email', nor does it specify prerequisites, contexts, or exclusions for its operations. Usage is implied through the listed functions but without explicit direction.

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