delete user

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is covered. The description adds valuable context: 'all owned data' is deleted and it executes a verified command 'v-delete-user', which signals a specific underlying operation. It doesn't mention irreversibility explicitly, but 'delete' plus 'all owned data' plus the destructive annotation makes that clear enough.

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?

Two short sentences with no filler. The core action and the key consequence ('all owned data') are front-loaded, and the command reference is a useful addition. Every word earns its place.

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 destructive tool with annotations covering the safety profile, the description is mostly adequate. However, it doesn't explain the 'restart' parameter or what happens after deletion (e.g., whether the user's data is permanently removed or recoverable). The output schema exists, so return values are covered, but the missing parameter semantics for 'restart' leave a 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 description coverage is only 33%, so the description should compensate for the undocumented parameters. The description mentions 'user' and 'all owned data' but doesn't explain the 'confirm' or 'restart' parameters. The schema itself documents 'confirm' as explicit confirmation for a destructive operation, but 'restart' has no description. The description adds minimal value beyond the schema for parameter semantics.

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 verb and resource ('Delete a user and all owned data') and adds the command it executes ('v-delete-user'). It is clear what the tool does, though it doesn't explicitly distinguish it from other delete_* siblings beyond the resource being a user.

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 implies this is the tool for deleting a user and all owned data, but it doesn't provide explicit when-to-use guidance or mention alternatives. The sibling list includes many delete_* tools, but the description doesn't say when to choose delete_user over them, which is fairly obvious from the resource name but not explicitly stated.

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