pve_node_rrddata

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

With no annotations, the description transparently states that the tool is read-only and describes the return format (list of data-point dicts with timestamps and metrics) and optional aggregation. It does not mention limitations like pagination or permissions, but is thorough for a telemetry fetch.

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 two sentences, front-loaded with the purpose, and contains no wasted words. It is well-structured and easy to parse.

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?

The output schema reduces the need to explain return values; the description summarizes the output well. It covers the main parameters (cf, timeframe) but does not explicitly differentiate from pmg_node_rrddata, though the name implies PVE vs PMG.

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 low (25%). The description adds meaning to 'cf' (consolidation function with AVERAGE or MAX) and implies 'timeframe' usage, but does not describe 'node' or 'proximo_target' beyond what the schema provides.

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 clearly states the action (Fetch), resource (RRD time-series telemetry for a PVE node), and read-only nature. It distinguishes from sibling tools like pmg_node_rrddata (PMG) and other PVE tools.

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?

The description provides context on what the tool does but does not give explicit guidance on when to use it vs. alternatives (e.g., pmg_node_rrddata) or when not to use it.

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