remnawave_users_bulk_reset_traffic

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

With no annotations provided, the description must disclose behavioral traits. It only labels the tool a 'mutation', which is implicit from the name. It fails to mention side effects, required permissions, or whether traffic is reset to zero, making it opaque.

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 sacrifices informativeness. It is not effectively concise; it omits critical details. A single sentence restating the name is under-specification.

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 tool's complexity (4 parameters with a nested payload object, no output schema, and no annotations), the description is grossly inadequate. It does not explain what the payload expects, the purpose of confirmToken, or the result of the mutation.

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 0%, yet the description provides no explanation for any of the four parameters (payload, confirmToken, responseMode, mutationApproved). The agent has no guidance on how to populate them.

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.bulk_reset_traffic (mutation)' barely adds beyond the tool name. It does not specify which users are affected (e.g., selection criteria) nor distinguishes from siblings like 'remnawave_users_reset_traffic' (single user) or 'remnawave_users_bulk_all_reset_traffic' (all users).

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 on when to use this tool versus alternatives. There is no mention of prerequisites, context, or when not to use it.

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