delete_whatsapp_account

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true, and readOnlyHint=false, so the safety profile is largely covered structurally. The description adds nothing on top: it does not say what gets destroyed (account record vs. associated phone numbers/conversations), whether the action is reversible, or what permissions are required.

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 words contain no waste but the brevity stems from under-specification rather than tight editing. There is nothing front-loaded to sequence because there is essentially no content.

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 destructive, irreversible-ish delete operation with no output schema and a completely undocumented parameter, the description is far too thin. Even with annotations covering the safety hints, an agent needs to know what the deletion removes and what confirmation guarantees apply.

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% and the description never mentions phone_number_id. The single parameter is self-descriptively named and the tool name implies which account is targeted, so an agent can partially infer intent, but no semantics (format, whether it can be a WABA id, whether it must exist) are supplied by either source.

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 is a verbatim restatement of the tool name ('delete_whatsapp_account' → 'Delete Whatsapp Account') with capitalization only. It conveys a verb and resource, but adds no scope, target, or differentiation from siblings like get_whatsapp_account, list_whatsapp_accounts, or update_whatsapp_account. This is the tautology case the rubric scores 2.

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?

There is no guidance on when to use this rather than the sibling get_whatsapp_account, list_whatsapp_accounts, update_whatsapp_account, or the generic delete_phone_number_route. No prerequisites, no confirmation/warning conditions for an irreversible operation are stated.

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