remnawave_bandwidth_stats_get_node_users_usage

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

The description only states '(read)', implying no side effects, but offers no details on behavior such as pagination, filtering, or response structure. Without annotations, this is insufficient for an agent to understand the tool's effects.

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, but conciseness sacrifices necessary detail. It is under-specified rather than efficiently informative.

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 no annotations, no output schema, and minimal description, the tool definition is incomplete. An agent would lack critical information to use it correctly, such as what the tool returns and how to structure requests.

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?

Description provides no explanation of parameters. Schema coverage is 0%, so the agent must infer meaning solely from parameter names and types, which is insufficient for parameters like 'payload' and '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 indicates it's a read operation for node users usage, which gives a basic sense of purpose. However, it largely repeats the tool name and lacks specificity on what data is retrieved, making it only marginally clear.

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?

There is no guidance on when to use this tool versus siblings like 'get_node_user_usage_legacy' or 'get_user_usage'. 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.