remnawave_system_get_nodes_metrics

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

The '(read)' label hints at non-destructive behavior, but no annotations exist to confirm. The description does not disclose authentication needs, rate limits, or any other behavioral traits beyond the read hint.

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 lacks substantive content. It is under-specified rather than concise, failing to provide meaningful information in its single sentence.

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 annotations, and 4 parameters including a nested object, the description is severely incomplete. It does not explain return values, error cases, or how the tool fits into the broader system.

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 explanations for the 4 parameters (payload, confirmToken, responseMode, mutationApproved). The 'payload' object and 'responseMode' enum remain undefined.

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 only repeats the tool name and adds '(read)', but does not specify what metrics are included (e.g., CPU, memory, traffic). It fails to differentiate from siblings like 'get_bandwidth_stats' or 'get_node_statistics'.

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 such as 'get_node_statistics' or 'get_health'. The description is silent on context or prerequisites.

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