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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds only 'Change a chat's state' and 'Requires chat_jid', which largely restates the mutation nature and a parameter requirement. It does not disclose effects, reversibility, permissions, or how unmute interacts with mute duration. There is no contradiction, but the added behavioral context is minimal.

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 short, but it wastes space on a generic action list and a machine-readable '[Flattened action: unmute]' tag. It could be replaced with a single specific sentence like 'Unmute a WhatsApp chat identified by chat_jid.' The structure is not optimized for the specific tool and includes redundant 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?

For a 3-parameter tool with no output schema and no enum constraints, the description is inadequate. It does not explain the operation's effect, prerequisites beyond chat_jid, or parameter meanings. The generic action list makes it difficult for an agent to know exactly what will happen when invoking this tool.

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 needed to explain chat_jid, account, and duration_secs. It only says 'Requires chat_jid,' which duplicates the schema's required field. It does not explain what a JID is, what account refers to, or that duration_secs is likely irrelevant for unmute (it belongs to mute).

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 opens with a generic 'Change a chat's state' and lists multiple actions (archive/unarchive, pin/unpin, mute/unmute) before noting '[Flattened action: unmute]'. It does not explicitly state 'Unmute a WhatsApp chat' as the tool's sole purpose, relying on the tool name and the flattened tag for disambiguation. This is more specific than a tautology but still vague and not clearly differentiated from sibling tools.

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 or whatsapp_chat_unarchive. The description mentions 'Requires chat_jid' as a prerequisite but does not explain that this tool is specifically for unmuting or how it relates to mute. The sibling list includes many similar chat-state tools, increasing the need for explicit usage guidance that is absent.

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