delete_user

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

Annotations already declare destructiveness and non-idempotency, but the description adds important behavioral context: the effect on sign-in, browser session termination, content retention, irreversibility, admin constraints, and the return shape. It does not contradict 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?

The description is compact and front-loaded: identity of the operation, access restriction, effects, constraints, irreversibility, and return value are all stated without filler. Every sentence carries operational meaning.

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 painless destructive admin tool with complete schema coverage and annotations, the description supplies all missing decision-critical context: irreversibility, session termination, content retention, self/last-admin exclusions, and return format. No output schema exists, so the return note is useful.

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%, so the input schema already documents both the 'id' and optional 'site' parameters. The description does not add further parameter-level syntax or meaning beyond what the schema provides, so the baseline 3 is appropriate.

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 states a specific destructive verb and resource (permanently delete a user account), names the admin-only restriction, and clearly differentiates the operation from sibling tools like create_user, update_user, and list_users. An agent can identify the exact action and scope without opening the 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?

It gives explicit usage conditions and exclusions: 'Admin only', 'you cannot delete yourself or the last Admin', and 'Irreversible'. These tell the agent when the tool is valid and when it must not be called.

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