remnawave_reset_user_traffic

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

Annotations already indicate idempotent and non-destructive behavior. The description confirms the action but provides no additional behavioral context (e.g., side effects, authorization needs, or rate limits). With annotations present, this is adequate but not enriching.

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?

A single, clear, and necessary sentence. Every word carries meaning. No redundancy or extraneous information.

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 simplicity (single parameter, clear mutation) and existence of an output schema, the description covers the essential action. It is complete for the purpose, though slight room for adding usage context.

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 already includes a description for the uuid parameter. The tool description adds no further semantic value. With high schema coverage (despite context signal stating 0%, the schema visibly contains descriptions), a score of 3 is appropriate.

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 clearly states the verb 'reset', the resource 'user's traffic counter', and the outcome 'to zero'. It uniquely identifies the tool's function among siblings that involve create, delete, enable, disable, and revoke actions.

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. The description lacks any contextual cues about prerequisites, scenarios, or exclusion cases. It is a single sentence with no usage direction.

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