system_nodes_statistics

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds nothing beyond that — no indication of aggregation scope, time window, cost, or what the statistics represent.

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 single phrase is not wasteful, but it is under-specified rather than concise — it conveys no actionable information beyond the title-like name.

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 tool with no output schema to explain return values, the description should describe what metrics are returned and the effect of the tz parameter. As written, an agent cannot predict the response shape or confidently invoke 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?

One parameter (tz) with 0% schema description coverage, and the description never mentions it or its timezone semantics. Since the parameter is fully undocumented in both schema and description, the description fails to compensate for the coverage gap.

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?

"Get Nodes Statistics" essentially restates the tool name (system_nodes_statistics) rather than stating a distinct verb+resource scope. It gives no hint of what statistics are returned or how they differ from siblings such as system_nodes_metrics, nodes_list, or system_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 tool versus the many neighboring read tools (nodes_get, nodes_list, system_nodes_metrics, hwid_stats). The agent is left to infer applicability entirely on its own.

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