remnawave_system_get_bandwidth_stats

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

The description labels the tool as '(read)', but the input schema includes 'mutationApproved' and 'confirmToken' parameters typical of mutation operations, creating a potential contradiction. No further behavioral traits are disclosed.

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 brief (one line) but fails to adequately explain the tool's functionality. It is concise at the expense of completeness.

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?

With no output schema, no parameter descriptions, and no annotations, the description is critically incomplete. The tool appears to accept a complex payload, yet no hints are provided about its structure or 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?

Schema description coverage is 0% and the description adds no meaning to the four parameters (payload, confirmToken, responseMode, mutationApproved). The agent cannot infer how to use the payload object or the purpose of confirmToken.

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 merely restates the tool name as 'Remnawave system.get_bandwidth_stats (read)' without specifying what bandwidth stats are retrieved (e.g., system-wide, aggregated). It does not differentiate from sibling tools like remnawave_bandwidth_stats_list_nodes_usage or remnawave_system_get_stats.

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 context, prerequisites, or exclusions.

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