remnawave_nodes_reset_traffic

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

With no annotations, the description only labels the tool as a mutation, but does not disclose side effects, required permissions, or confirmation steps, despite the schema having parameters for confirmation.

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 (one sentence), but it is too sparse to be effective. Conciseness should not come at the expense of clarity.

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 lack of output schema, no annotations, and four undocumented parameters, the description is woefully incomplete. The agent cannot safely or effectively invoke this tool without external documentation.

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 offers no explanation for the four parameters (payload, confirmToken, responseMode, mutationApproved). The agent receives no help understanding what each parameter does.

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 identifies the tool as a mutation to reset traffic for nodes, but it is vague about what exactly is reset (e.g., traffic counters) and lacks specifics to distinguish it from sibling tools like '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 like node disabling or deleting. The description does not mention prerequisites or typical use cases.

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