remnawave_users_reset_traffic

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

Description mentions 'mutation' but does not disclose side effects, such as whether traffic counters are zeroed, or that confirmation may be required (indicated by confirmToken and mutationApproved in schema). No annotations to supplement.

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?

Single sentence, very short, not verbose. However, it is under-specified and lacks structure, making it minimally helpful.

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 4 parameters, no output schema, and no annotations, the description is inadequate. It does not cover confirmation requirements, payload structure, or return behavior.

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 has 4 parameters with 0% description coverage. The description does not explain any parameter, leaving the agent to infer from names like payload, confirmToken, responseMode, mutationApproved.

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 states 'users.reset_traffic (mutation)', indicating it resets traffic for users. However, it lacks specificity about what exactly is reset and does not differentiate from sibling tools like remnawave_users_bulk_reset_traffic or remnawave_nodes_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 on when to use this tool versus alternatives. There are multiple similar tools for bulk operations, and the description provides no context for selection.

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