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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not explain whether exporting is read-only, whether files are created, what permissions are needed, how pagination works, or what the response looks like beyond the selected format.

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 brief and front-loaded with the core export purpose. The second sentence usefully points to the related analyze action, though it adds slight ambiguity by referencing an action parameter not present in this tool's schema.

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 rich schema covers all ten parameters, so invocation details are mostly available elsewhere. Still, for a complex export tool with no annotations and no output schema, the description should do more to explain the returned data or file behavior and any operational constraints.

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 parameter semantics are already well documented in the input schema. The description adds only a general mention of export formats and does not provide additional meaning for parameters such as limit, status, dates, fields, or verbosity.

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 a specific verb and resource: exporting a WhatsApp chats list in multiple formats. It also relates itself to analyze_whatsapp_chats with the export action, but it does not distinguish itself from many other chat-listing siblings such as get_whatsapp_chats or search_whatsapp_chats_by_name.

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?

It gives broad use cases such as backup, analysis, and reporting, which implies when the tool is useful. However, it does not explicitly say when to choose this tool over analyze_whatsapp_chats or the several get/search chat tools, nor does it state exclusions or prerequisites.

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