Delete Reseller User

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known; the description adds value beyond that by disclosing the cascade scope ("everything under it"), the irreversibility, the possibility of failure per DirectAdmin behavior, and the auth-context requirement. Nothing here contradicts the annotations.

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?

Four tight sentences with the danger warning front-loaded before auth and error details, and no padding. The phrase "may fail or cascade" is somewhat hedged and could be sharper, but nothing is wasted.

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 one-parameter destructive tool with an output schema already available, the description covers everything an agent needs to act safely: scope of deletion, auth context, and error interpretation. Return values are correctly left to the output schema.

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% — the single username parameter already carries type, pattern, length, and character rules. The description only adds the caution to double-check the username first, which is operational advice rather than new semantics, so 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?

Opens with a specific verb and resource ("deletes the user and everything under it") and immediately scopes the blast radius. An agent can distinguish it from suspend_reseller_user, delete_domain, and delete_email_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 a clear precondition that is easy to get wrong — call while authenticated as the plain reseller, not while impersonating a user — and explains what a 404 means. It does not explicitly route an agent to the non-destructive alternative (suspend_reseller_user) when reversibility is desired, which keeps it short of a 5.

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