whatsapp_create_contact

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

With no annotations provided, the description carries full burden for behavioral disclosure. It merely states 'Create or update,' which is a basic hint of write operations, but fails to describe required permissions, side effects (e.g., overwriting existing contacts), or whether updates are partial or full replacements.

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 extremely concise at 3 words, front-loading the core purpose. It is efficiently structured but could benefit from a bit more context without sacrificing 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?

The description is too minimal for a tool that creates/updates contacts. It lacks information about return values (e.g., the updated contact object), error handling, and the distinction between create and update behavior. The absence of output schema further amplifies the need for descriptive completeness.

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?

The input schema covers 100% of parameters with individual descriptions, so the description adds no extra meaning beyond the schema. The baseline is 3, and the description does not elaborate on how parameters interact (e.g., if 'firstName' is optional and what happens when omitted).

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 the action 'Create or update a WhatsApp contact,' which is a specific verb and resource. It is distinct from sibling tools like 'whatsapp_get_contact' or 'whatsapp_block_contact.'

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 such as 'whatsapp_get_contact' or 'whatsapp_sync_contacts.' It does not mention prerequisites, when not to use it, or any context for creation vs. update scenarios.

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