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

No annotations are provided, so the description carries the full behavioral burden. It implies a read operation via 'search and filter' but does not explicitly state non-destructiveness, permission requirements, rate limits, or pagination behavior beyond what the schema already documents.

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 front-loaded and efficient, using two short sentences plus an equivalence note. The final sentence adds routing value, though the phrase 'Same as get_whatsapp_chats' could be slightly ambiguous without knowing that tool's action parameter.

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?

For a read-only list tool with full schema coverage and no output schema, the description covers the core purpose. It lacks guidance on return format and does not clearly differentiate from near-sibling tools like get_whatsapp_archived_chats, leaving the agent to infer selection.

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 all parameters including the status enum are already well documented in the schema. The description mentions the status filter and gives examples, but adds no syntax or format details beyond the schema baseline.

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 (search/filter) and resource (WhatsApp chats), plus the filtering dimension (platform status). It also clarifies equivalence to get_whatsapp_chats with action 'by_status', which helps distinguish it from that sibling. However, it does not resolve overlap with specialized siblings like get_whatsapp_archived_chats.

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 gives implied usage ('useful for workflow management and chat organization') and points to get_whatsapp_chats as the general form. It does not explicitly state when to choose this tool over dedicated siblings such as get_whatsapp_archived_chats or get_whatsapp_assigned_chats.

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