get_nodes_statistics

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no indication of what the statistics cover, freshness, aggregation window, or response shape. The '[READ]' tag merely repeats the annotation.

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?

Two short lines with zero padding and the resource name front-loaded. However, this brevity reflects under-specification rather than disciplined conciseness; nothing meaningful was cut because nothing meaningful was present.

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?

For a statistics endpoint with no output schema and an undocumented parameter, the description should at minimum say what data is returned and what the parameter does. It provides neither, so an agent cannot confidently invoke or interpret it.

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% for the single 'tz' parameter, so the description carries the full burden — but it says nothing about it. The agent cannot tell that 'tz' is a timezone affecting how statistics are bucketed.

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 is essentially the tool name restated ('Get Nodes Statistics') plus a raw HTTP route. It does not say what statistics are returned or how they differ from the many sibling stats tools (get_stats, get_nodes_metrics, get_stats_nodes_usage, get_hwid_devices_stats). Only the '/api/system/stats/nodes' path hints at system-level node 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 on when to use this versus the numerous other stats/metrics endpoints. There is no statement of preconditions, scope, or alternatives, leaving the agent to guess from the name alone.

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