remnawave_users_delete

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states 'mutation', which is clear from the operation name. There is no information about the effects of calling the tool, the role of parameters like confirmToken or mutationApproved, or any side effects.

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 extremely concise, but it is under-specified to the point of being unhelpful. It consists of a single phrase that adds no new information, making it more of a tautology than a concise, informative summary.

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?

Given the complexity of the tool (4 parameters, no output schema, nested objects, and many sibling tools), the description is severely lacking. It does not explain how to use the parameters, what the payload should contain, or how it differs from similar tools like bulk delete. This is inadequate for an AI to use correctly.

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%, so the description must explain parameter meaning, but it does not. Parameter names like 'payload' and 'confirmToken' are somewhat self-explanatory, but the complex 'payload' object is left completely undocumented. The description adds no value beyond raw schema.

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 'Remnawave users.delete (mutation)' essentially repeats the tool name and adds '(mutation)', which is already implied by 'delete'. It fails to specify whether the tool deletes a single user or multiple users, and does not distinguish it from sibling tools like 'remnawave_users_bulk_delete'.

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?

No guidance is provided on when to use this tool versus alternatives such as bulk delete. There is no mention of prerequisites, context, or exclusion criteria.

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