Log out or delete an account

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description goes further by specifying what is destroyed (account and messages), that delete cannot be undone, that it fires no event, that billing stops in both cases, and that confirm: true is required for every action. This is exactly the added behavioral context annotations alone cannot convey.

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?

Front-loaded summary followed by an action list is easy to scan, and the irreversible-delete warning appears in the right place. Minor redundancy: 'log the number out and stop billing' is stated once in the intro and again in each bullet.

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 mutation tool with no output schema, the description covers the decision between modes, the irreversibility boundary, the confirm gate, where accountId comes from, and even what logout returns. Nothing material an agent needs to call this safely is missing.

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 the schema already documents action, confirm (const true), and accountId, including the constraint to set confirm only after user agreement. The description restates the confirm requirement but adds no syntax or format detail beyond the schema; baseline 3 applies.

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 and resource ('Unlink a WhatsApp number from wuapi') and immediately disambiguates the two modes it supports. An agent can tell it apart from siblings like reconnect_account or update_account without opening any schema.

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?

Gives explicit selection criteria for both actions: 'logout' to keep the account and its stored messages, 'delete' to remove the account for good. It also names the follow-up path (reconnect_account shows a new QR code), so the agent knows which action to pick and what happens next.

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