remnawave_users_bulk_all_reset_traffic

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

With no annotations, the description carries the full burden of behavioral disclosure. It only labels the tool as a 'mutation', which is obvious from the name. It does not disclose what traffic resetting entails, whether it is irreversible, or what permissions are needed. Parameters like confirmToken and mutationApproved are not explained.

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 short, but this sacrifices completeness. It is under-specified rather than concise. One sentence that says nothing beyond the name and type is insufficient.

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 a bulk mutation tool with no annotations, no output schema, and multiple parameters, the description is woefully incomplete. It fails to provide essential context for safe and correct usage.

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 has 4 parameters with 0% description coverage in the schema, yet the description adds no information about them. The 'payload' object is left undefined, and the purpose of confirmToken, responseMode, and mutationApproved is not clarified.

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?

Description merely restates the tool name as 'users.bulk_all_reset_traffic (mutation)' without explaining what it does. It does not clarify that it resets traffic for all users, nor does it distinguish it from similar sibling tools like remnawave_users_bulk_reset_traffic or remnawave_users_reset_traffic.

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. There is no mention of prerequisites, side effects, or scenarios where this tool is appropriate.

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