Supabase: Delete user

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

Annotations already declare destructiveHint=true and idempotentHint=false, so safety is covered structurally; the description's contribution is the cascade scope ("all their data"), which is genuinely useful beyond the annotations. It omits auth/permission requirements, whether deletion is recoverable, and any confirmation step expected before an irreversible operation.

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?

A single front-loaded sentence with no filler, but the unexplained "[UNIFIED]" prefix adds noise without meaning, and the brevity leaves critical semantics unaddressed rather than being efficiently dense.

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 an irreversible destructive tool with zero schema description coverage, no output schema, and no annotations explaining permissions, the definition says far too little. It never clarifies what "all their data" includes, whether the action requires elevated privileges, or how failure is reported.

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% for two required parameters, so the description carries the full burden and offers nothing about what "site" identifies or what form "user_id" takes (UUID, email, etc.). With zero compensation for a total coverage gap, this falls below the baseline.

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 ("Permanently delete a user") plus the blast radius ("all their data"), which separates it from soft alternatives like supabase_ban_user. It does not explicitly name any sibling, so differentiation is inferred rather than stated.

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 choose this over supabase_ban_user, supabase_delete_user_factor, or other user-removal tools, and no prerequisites or warnings about irreversibility beyond the word "permanently". The agent must infer usage entirely.

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