whm_terminate_account

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

The description warns of permanent deletion and data loss, but does not disclose additional behaviors like the need for confirmation (though confirm parameter is in schema), irreversibility, or what happens to associated resources. Lacks details beyond the basic destructive nature.

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?

Single sentence with an emoji warning conveys the essence immediately. No fluff, well front-loaded.

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 tool with no annotations and no output schema, the description is minimal. It does not explain return values, prerequisites (e.g., account existence), or side effects beyond data loss. Could include more context like requiring confirmation or suspending first.

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 67% (account and confirm have descriptions, username does not). The tool description adds no extra meaning beyond schema; account description already references list_accounts, confirm description already states must be true. Username remains undocumented.

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 clearly uses strong verbs 'PERMANENTLY DELETE' and specifies the resource 'a cPanel account and all its data', distinguishing it from sibling tools like whm_suspend_account (temporary suspension) or whm_create_account.

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?

The description implies permanent deletion but provides no explicit guidance on when to use this tool vs alternatives (e.g., when to suspend vs delete). No scenario or prerequisite information is given.

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