Delete a user

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

Beyond the destructiveHint annotation, the description discloses the concrete consequence: the account is removed and its pages must be reassigned to another user. It also reveals the non-obvious confirmation-token requirement, adding valuable behavioral detail that an agent could not infer from annotations alone.

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?

Three short sentences, with the core action front-loaded and no redundant filler. Every sentence contributes either to the primary purpose or to essential invocation requirements.

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?

The description captures the essential two-step confirmation workflow and the required replacement parameter, while the schema fully documents the token's optionality and format. No output schema exists, but for a destructive action, the absence of return-value details is a minor gap.

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 100%, so a baseline of 3 applies. The description adds meaningful semantic value by explaining why replace_with_user_id is required and what the confirmation token is for, going beyond the schema's brief field descriptions.

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 the direct action 'Removes an account,' clearly identifying the verb and resource. It further distinguishes itself by explaining the account inheritance requirement, which is unique to user deletion among the delete_* sibling tools.

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 gives clear operational context, explaining that replacement ownership is mandatory and that a confirmation token is needed. It does not explicitly name alternative tools or state when not to use it, but the deletion context is unambiguous.

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