users_delete

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

With no annotations, the description carries the behavioral burden. It does state 'permanently delete', which conveys the critical destructive and irreversible nature, and it flags confirm as required. However, it does not explain cascading effects on the account's data, domains, email, or reseller sub-accounts, nor what permissions are needed.

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 two short sentences plus a compact args list, with the core purpose front-loaded. There is no filler or repetition of schema metadata, and the structure makes the destructive action immediately visible.

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 two-parameter destructive tool, the description covers the essential action and argument names, and an output schema exists so return values need not be documented. Still, an agent is left to guess the exact confirmation payload and the scope of deletion, which is risky for an irreversible operation without annotations.

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 must compensate. It adds 'username: Account to delete' and identifies confirm as required, but it does not specify that confirm must be set to true or describe its type. This is further muddled by the schema, where confirm is optional with default false, directly conflicting with the description's 'Required'.

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 'Permanently delete a user/reseller/admin account', stating the exact verb, resource, and irreversibility. This clearly separates it from nearby siblings like users_suspend or users_modify, which imply temporary or partial changes.

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 choose this tool over alternatives such as users_suspend, users_unsuspend, or users_modify. The description never mentions exclusions, prerequisites, or that this should be reserved for accounts that must be removed permanently.

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