whatsapp_sync

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

'Returns right awa...' (truncated) suggests it returns immediately before the sync completes, which is a critical behavioral trait - it implies an asynchronous operation. But this is cut off and incomplete, and with no annotations, the description leaves key behaviors (auth requirements, whether it blocks, error handling) undocumented. The truncated text severely limits 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 sentence but is truncated at 'returns right awa...', which is a severe structural flaw for an agent-facing definition. The front-loaded verb is good, but the incomplete sentence fails to deliver critical information.

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?

No output schema, no annotations, and the description is cut off mid-word. For a tool that appears to trigger an async background sync, an agent needs to know it returns immediately, whether to poll for completion, and what state it populates. The truncation makes this incomplete.

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?

Zero parameters, so baseline 4 applies. The description doesn't need to explain parameter semantics since none exist, and it doesn't confuse the matter.

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 a specific verb (pulling) and resource (messages, groups, contacts into the local store), which is clear enough. However, with many WhatsApp siblings (whatsapp_read_messages, whatsapp_list_groups, whatsapp_search_messages), it doesn't clearly distinguish sync from read/list operations - the relationship (sync populates the store that reads use) is not spelled out.

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 implies this is a startup/refresh operation via 'Starts WhatsApp pulling', but it doesn't explicitly state when to use sync vs whatsame_read_messages or whatsapp_list_chats. An agent must infer that sync should be called before reading, without confirmation.

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