whatsapp_mute_chat

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

Annotations carry the safety profile (idempotent, non-destructive, open-world). The description adds genuinely useful context beyond them: 'Only affects this account; the other side is not told' discloses the local-only scope, and the return confirmation is noted even though no output schema exists.

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?

Three short, front-loaded sentences with no filler. Each sentence carries distinct information: action, scope/side-effect, and return behavior.

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 2-parameter tool with full schema coverage and rich annotations, the description covers purpose, side effects and return adequately. The only gap is lack of sibling differentiation, which is minor given the clear 'chat' resource.

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 coverage is 100% with an enumerated duration, so the schema does the heavy lifting. The description's phrase 'or unmute it' marginally clarifies that the 'off' enum value means unmute, but otherwise adds little beyond the schema.

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?

States a specific verb (mute/unmute) and resource (a chat's notifications), and the dual nature (mute or unmute) is clear. It does not explicitly differentiate itself from the sibling whatsapp_mute_newsletter, though the 'chat' resource is unambiguous.

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?

Usage is implied by the duration enum semantics ('off' = unmute) rather than stated. There is no explicit when-to-use guidance, no mention of prerequisites, and no routing to sibling tools like archive_chat or mute_newsletter.

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