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

The description adds little beyond the annotations: it says 'Change a chat's state' but does not explain side effects, reversibility, permissions, or the meaning of the missing 'action' parameter. The annotations (readOnlyHint=false) are consistent with a mutation, but the description fails to disclose what actually happens or what the '[Flattened action: archive]' note means.

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 text is brief and front-loaded with the main verb, but the structure is muddled: it mixes a general action list with a cryptic note about a flattened action. The 'action:' list reads like a parameter specification but is not backed by the schema, creating confusion rather than concise clarity.

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 3 parameters, missing output schema, and many related sibling tools, the description is incomplete. It does not explain how to specify an action (since no action parameter exists in the schema), what duration_secs is for, or how this tool relates to the dedicated archive/unarchive/mute/pin tools, making it hard for an agent to invoke correctly.

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?

The schema lists 'account', 'chat_jid', and 'duration_secs' with no descriptions, and the description only mentions 'chat_jid' as required (already declared in schema). It introduces an 'action' concept that is not present in the schema, and does not explain 'duration_secs' or 'account', leaving parameter meaning unclear.

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 it changes a chat's state and lists specific actions (archive/unarchive, pin/unpin, mute/unmute), which gives some clarity. However, the tool name 'whatsapp_chat_archive' and the note '[Flattened action: archive]' conflict with the broader scope, and it does not distinguish itself from the many sibling tools that cover the same individual actions.

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 like whatsapp_chat_mute, whatsapp_chat_pin, or whatsapp_chat_unarchive. The only hint is 'Requires chat_jid', which is a prerequisite already present in the schema, not a usage context.

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