WhatsApp MCP for macOS

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating a safe read operation. The description adds useful behavioral context about ordering ('ordered by last message time') and filtering capabilities, but doesn't mention pagination, rate limits, or authentication requirements. With annotations covering safety, this adds moderate value.

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 efficiently structured with a clear purpose statement followed by parameter explanations in a bullet-like format. Every sentence adds value without redundancy, and it's appropriately sized for a simple list tool.

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 low complexity (2 simple parameters), rich annotations (readOnlyHint, destructiveHint), and existence of an output schema, the description is reasonably complete. It covers purpose and parameters adequately, though it could benefit from more explicit usage guidance relative to sibling tools.

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 0%, so the description carries full burden. It clearly explains both parameters: 'limit' specifies number of chats with a max constraint, and 'chat_type' defines filter options with enum values. This adds meaningful semantics beyond the bare schema, though it doesn't cover default values or format details.

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 specific action ('List recent WhatsApp chats') and resource ('WhatsApp chats'), with explicit ordering ('ordered by last message time'). It distinguishes from siblings like whatsapp_search_contacts or whatsapp_get_messages by focusing on chat listing rather than contact search or message retrieval.

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 usage for retrieving chat lists but provides no explicit guidance on when to use this tool versus alternatives like whatsapp_search_contacts or whatsapp_get_messages. No exclusions or prerequisites are mentioned, leaving usage context to inference.

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