system_get_nodes_metrics

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

No annotations are provided, so the description carries the full behavioral burden, yet it only implies a read via the HTTP verb. It says nothing about authentication requirements, whether metrics are current vs. historical, aggregation window, or response shape. A bare endpoint string is far short of what an unannotated tool needs.

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?

It is short and contains no padding, but the content is mostly raw HTTP boilerplate rather than an agent-oriented summary. The 'Tags: System Controller' line is the only mild routing signal, and it is placed last rather than front-loaded with actual meaning.

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 parameters, no output schema, and no annotations, the description is the only source of information, and it omits what the metrics are, their granularity, and the expected response. For a metrics-retrieval endpoint with output-schema absence, this is under-specified.

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?

The tool takes zero parameters, which is the baseline-4 case. There is nothing for the description to compensate for, and no misleading parameter hints are given.

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 a restatement of the tool name: 'GET /api/system/nodes/metrics' plus 'Get Nodes Metrics'. It tells the agent this retrieves node metrics, but nothing about which metrics or how it differs from close siblings like system_get_nodes_statistics, system_metrics, or nodes_usage_history_get_stats_nodes_usage. This is tautology territory rather than a specific verb+resource distinction.

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 when-to-use guidance, no prerequisites, and no mention of alternatives, despite several overlapping siblings that also surface node/system metrics. The agent must infer applicability 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.