remnawave_system_get_node_statistics

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

The description indicates it is a read operation, but with no annotations, it fails to disclose other behavioral traits such as authentication requirements, rate limits, or potential side effects. Minimal transparency.

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?

Extremely brief, but the brevity omits essential details. A longer description is needed for a tool with 4 parameters and no output schema.

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 and no description of return values, the agent cannot understand what the tool provides. The description is inadequate for this 4-parameter tool.

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 information about parameters like 'payload', 'confirmToken', or 'responseMode'. The tool's purpose is unclear regarding how parameters affect behavior.

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 retrieving node statistics (read), which is a clear verb-resource pair. However, it does not specify which nodes or what type of statistics, making it less specific than optimal.

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 siblings like 'remnawave_system_get_stats' or 'remnawave_system_get_nodes_metrics'. 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.