Sync WhatsApp Contacts

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

The description does not disclose important behavioral traits such as whether existing contacts are overwritten, if duplicates are merged, if the operation is idempotent, or if any prerequisites (e.g., connected WhatsApp channels) are required. With no annotations to compensate, this is a significant gap for a sync 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 a single, well-formed sentence that directly states the purpose. It is appropriately sized with no filler, front-loading the essential action and resource.

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?

Despite having no parameters and no output schema, the description omits critical context about the sync behavior (e.g., additive vs. destructive, safety of repeated calls, dependency on prior channel setup). This leaves the agent underinformed for a potentially impactful operation.

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?

There are no parameters, so the schema coverage is trivially 100%. Baseline for zero parameters is 4, and the description does not mislead or need to add parameter info. It appropriately indicates no configuration is needed.

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 specifies a clear verb ('synchronize') and resource ('contacts from connected WhatsApp channels into the contacts database'). It implies a bulk sync operation and is somewhat distinct from related siblings like 'neuron_create_contact' or 'neuron_list_whatsapp_contacts', though could be confused with 'neuron_populate_contacts'. Score is 4 due to lack of explicit 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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'neuron_create_contact' for individual additions or 'neuron_import_contacts' for file imports). There is no mention of prerequisites, exclusions, or context for when syncing is appropriate.

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