remnawave_delete_user

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

Annotations already inform destructiveHint=true, readOnlyHint=false, idempotentHint=false. The description adds 'This action cannot be undone,' reinforcing the destructive nature. However, it does not disclose side effects, permission requirements, or consequences for associated data (e.g., subscriptions). The additional context is minimal given the annotation coverage.

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 concise sentences that front-load the core purpose and include an important behavioral note. Every sentence earns its place with no unnecessary information.

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 simple destructive tool with one parameter and annotations already covering readOnly/destructive aspects, the description is sufficient. The output schema exists (not shown) so return values need not be described. A brief mention of confirmation or rollback (e.g., 'no undo') could improve completeness but is not essential.

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?

The input schema defines the uuid parameter with description 'UUID of the user,' so schema coverage is effectively 100% at the parameter level. The tool description does not add any extra meaning beyond what the schema already provides. Baseline score of 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 clearly states the action 'Permanently delete a user by UUID' with a specific verb (delete) and resource (user). It identifies the required parameter (UUID). However, it does not differentiate from sibling tools like remnawave_disable_user or remnawave_revoke_user, which have similar but distinct operations.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, conditions, or scenarios where deletion is appropriate (e.g., irreversible removal vs. disabling). The agent receives no context for decision-making.

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